[nrdo-list] Transactions

[Nick Warner]

We’ve experienced an issue with Sql transactions and are wondering if you have any suggestions.

Our issue is as follows:

We are using ADO.NET 2.0 with an Sql Server 2000 database. When using the TransactionScope object to control our individual updates of each data-aware NRDO object, everything works fine when the application is hosted on our Windows 2003 development server. When we move the project to our local machines, however, we receive an error that states “The transaction manager has disabled its support for remote/network transactions.”

Upon researching the TransactionScope class, the MSDN documentation specifically references Sql Server 2005 as the database of choice, since that configuration will not invoke the distributed transaction coordinator. We believe that the issue we are experiencing is caused because we are not running Windows Server on our development machines (in other words, we can prove that the full-blown server components handle this situation just fine).

What we would like to do is use our local machines to host our individual development environments, but we all want to access the same Sql Server 2000 database on the development server. Any suggestions?

Nick Warner
Developer
Transaction Management, LLC.
817.284.9607 x3012
address@hidden

CONFIDENTIAL COMMUNICATION
This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you receive this communication in error, please notify us by your e-mail reply feature and delete the original message and destroy any copies thereof.