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? Thanks, Shawn Wildermuth [EMAIL PROTECTED] http://adoguy.com http://shawnwildermuth.com "...for the programmer, as for the chef, the urgency of the patron may govern the scheduled completion of the task, but it cannot govern the actual completion. An omelette, promised in two minutes, may appear to be progressing nicely. But when it has not set in two minutes, the customer has two choices--wait or eat it raw. Software customers have had the same choices. The cook has another choice; he can turn up the heat. The result is often an omelette nothing can save--burned in one part, raw in another.... " - Brooks, The Mythical Man-Month. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
