Hi Keith,

That is correct. The problem here is that the DeriveParameters method needs to make a trip back to the database and it runs under a separate connection. You need to run this method prior to beginning your transaction.

>It seems that SqlCommandBuilder.DeriveParameters will not participate in a transaction when the SqlCommand that it uses has a transaction assigned to it.
>
>This can be a real PITA to track down when combined with the Data Application Block's parameter caching. I pulled my hair out for two days isolating this sucker.