Concurrency violation - concurrency_error_watch.xls (0/1)

  • Thread starter Thread starter nick
  • Start date Start date
Hi Nick,

I reproduced the problem on my side. However, due to the complexity of this
issue, I will need more time to investigate. Thanks for your patience.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Nick,

I reproduced the problem on my side. However, due to the complexity of this
issue, I will need more time to investigate. Thanks for your patience.
Click to expand...

No worries. Thanks again for your help.
 
Hi Nick,

I reproduced the problem on my side. However, due to the complexity of this
issue, I will need more time to investigate. Thanks for your patience.
Click to expand...

Don't mean to rush you but just like to know if you have any progress.

Cheers.
 
Hi Nick,

This issue seems strange. To narrow down the problem, I built a simple
project of my own which works properly on updating the dataset. I am now
digging into your project to see what's going wrong.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hello Nick,

Thanks for your patience. After further research on this issue, I found out
that the problem was caused by the improper order of SQL parameters. Based
on my research, the OLE DB Provider handles parameters differently than
SQLClient which accepts named parameters. Please adding the parameters in
the correct order and see if it works on your side:

oleDbDataAdapter1.UpdateCommand.Parameters.Add("@dancerid",
OleDbType.BigInt,4, "dancerid");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@len", OleDbType.Integer,1,
"len");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@start",
OleDbType.VarChar,5, "start");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@pdancer",
OleDbType.Integer,2, "pdancer");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@pclub",
OleDbType.Integer,2, "pclub");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@room",
OleDbType.VarChar,1, "room");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@finished",
OleDbType.Boolean,1, "finished");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@cancelled",
OleDbType.Boolean,1, "cancelled");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@paid",
OleDbType.Boolean,1, "paid");
oleDbDataAdapter1.UpdateCommand.Parameters.Add("@privateid",
OleDbType.BigInt,4, "privateid");

I am standing by for your result.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hello Nick,

Thanks for your patience. After further research on this issue, I found out
that the problem was caused by the improper order of SQL parameters. Based
on my research, the OLE DB Provider handles parameters differently than
SQLClient which accepts named parameters. Please adding the parameters in
the correct order and see if it works on your side:
Click to expand...

Damn didn't think of that possibility... Thanks a bunch!

Gotta read more into OleDbCommand.Parameters when I got time :)
 
Back
Top