> Shawn Wildermuth spake: > > I just want to confirm this. CommandBuilders and transactions are > incompatible, right? Since the CommandBuilder generates and destroys > Command objects on the fly as needed, I assume there is no way to attach > a transaction to the commands. I want to update a database with > standard optimistic concurrency, but I want to wrap the entire thing in > a local transaction to make sure that all table updates are completed > together. > > Ideas?
No this is incorrect. The CommandBuilder requires a SelectCommand (which is where the update metadata is calculated from). When the CommandBuilder generates Update, Insert, and Delete commands it inherits the Transaction property from the Select command. -- Peter You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
