>What that error means? Something's wrong in my transaction?
>
>Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 106) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

While I'm not MS SQL export, I agree with every thing that Dragan said. I help support a program that was written in MS SQL 6.5 that does this constantly (the front end is built in PowerBuilder, I think). Version 6.5 used "page locking" while new versions use "record locking." The chance of getting a "deadlock" error is much greater with version 6.5 than say SQL 2000. The other issue that causes our "deadlocks" is that we have twice as many users than the application calls for, thus the opportunity for dead locks is great since it was designed to handle the volume we are pushing through it. Worst yet, much of the code does not trap for this error and then resubmit the data update so I've written several VFP routines that run in the background picking up the "deadlocks" and resubmitting them.

Robert