Hi Borislav,

Your response is similar to mine. In that VFP passes a transaction back to SQL Server to handle and at that point vfp must just wait until SQL Server returns a result. Thus it sort of makes sense that the SET REPROCESS command would likely NOT have any impact on SQL Server (but I though I would ask just in case my understanding was incorrect). However, this state of waiting indefintetly for a result to be returned from SQL Server poses a problem.

If SQL Server is waiting for a lock and could wait for a long time depending upon other activity, then a TABLEUPDATE() in VFP is in effect hung until SQL Server returns a result. I am exploring ways to allow VFP to determine how long it is going to wait for SQL Server to return a results so as to prevent that "hung workstation" conditions from happeneing.

Or figure out how to tell SQL Server how long it is to wait for a lock since the default seems to be indefinetly.