>Hi Edward and also others
>
>The very problem that I have when using the combination of the two is that it gives an intermetent error i.e. "wait...record is not available" which forces the user to reset the computer or end the task. This often occurs when two or more workstation runs the same module and clicked simultaneously the SAVE button that have the BEGIN...TABLEUPDATE..END TRANS codes. As I have said in my previous message, I just eliminated the BEGIN...END TRANS and everything runs smoothly. The BEGIN...END TRANS is very important in a C/S especially in an enterprise environment which have hundreds of users using the application. Any work around on this so far?

Jess,

You are getting that error because of how you have SET REPROCESS set up. Transaction lock resources and if you have fox set to reprocess lock requests forever then the transaction will sit there an try to get a lock it can't get forever, Lower the reprocess setting and then let the transaction fail if there is contention. You can always recover from the failure later.