Hello Nancy!

>I am confused, did you _try_ changing the SET REPROCESS from AUTOMATIC? Just to see what happens?

Nope so far. I just eliminated the Tx's commands. I think the only difference is just retrying the process indefinitely or for a definite time. But what irritates me is that no more open workstations other than the current one but the creeping "wait..." is still there as it seems it can not lock the table. Another thing is that the app has been distributed to a couple of clients. With that, changing the SET REPROCESS (if that would be the case) seems not realistic at this time.

>>>>You may doubt it but the team is composed of 3 persons only. Before we deliver the product we see to it that it was properly QA'd if there is such a term. The 2 workstations has been downed. That's why I call it weird and intermittent.
>>>
>>>And did you insure that the workstation still running wasn't holding a lock on something somewhere else in the system causing the failure of the transaction to get its lock?
>>
>>No other modules opened. We use VFP6 SP3. Private Datasession.