>No other modules opened. We use VFP6 SP3. Private Datasession.
Jess,

Here's the story. The error you mentioned indicates that something somewhere has the table your transaction is trying to lock and so the trnasaction is trying forever. It tries forever because you SET REPROCESS AUTOMATIC and the lock is occupied by something else somewhere. If it was not anything you have looked at, then it is something you have not looked at. If you have looked at everything, then it can only be goblins in your computer, but I very much doubt that there are any goblins. So, there is something you haven't looked at.

I am a bit tired of the "Look at this", "we looked at that" game. Read the previous paragraph carefully and finish your debugging. Stop looking at the transaction for the problem that is not where it is.

This reminds me of the guy who approached his friend under a street light searching on the ground, he asked "What did you lose?" The friend answered, "My contact lens." The guy then said, "Well isn't lucky you lost it right here under the street light." To which his friend said, "No, I lost it over there but the light is better over here."