We opened a case with MS last Thursda. THe problem is reproducable, I can recreate it from my station against our prod server as I need. The same parameter is corrupted...

Yes, I meant DataAdapter.InsertCommand. Thanks.

Still it seems that our problem is not attached to a specific param. It is rather a more or less specific place in the SQL...

Hey, Carl. Post it here if you find something.

If we can not get our answers from forums today, we are opening support case with MS. We'll see what they can do...

Thanks, Steve, for trying to come up with some ideas.

Basically, we are hoping someone would have a precedent of this kind. Our trouble is that we can not even replicate the...

Hey, Steve.

This specific param name maps to a field name in a database table. It became a param because the DataSet sets it up this way. The only code we...

Steve, here is a snippet to look at. thanks

// create and load dataset

// ...

sqlConnection1.Open();

SqlTransaction transaction =

sqlConnection1.BeginTransaction("UpdateOptionsTransaction");

try

{

// Add transaction to UpdateCommand, InsertCommand, and DeleteCommand for all our DataAdapters

daCleanups.UpdateCommand.Transaction = transaction;

// ......

Thanks for trying to help.

But notice that I am talking about corrupting the SQL parameter *name*, not the value in it. I do not think the corruption has to do with the...