Randall,

How does the second user "get" the record? From Help:

"If the lock or locks are successfully placed, RLOCK( ) returns true (.T.). Locked records are available for both read and write access by the user who placed the locks and for read-only access to all other users on the network."

That means an SQL statement or a COPY TO will pick up the record even when it is locked. You could always put a semaphore bit in the record and have the user set it when (s)he begins to edit, and only copy unset records. Or the other way around, have the copy code set a bit that the record has already been extracted.




>I have a case where a user can be modifying a record and another user runs an app and copies the record anyway. Example. My usewr is in there editing record number 14. They have not hit save yet. Another user runs an app and record 14 applies to what they want so the app copies the record to another table. The app should then go back and delete the record in the previous table but does not. I thought I had pessimistic choosen as a whoe in my preferences but maybe Iam missing something. The result we have now is that the record in in both tables and can be accidently edited and sent out again. Any wayb to assure that if a user is using a record that another app or person can't come along and get it?
>
>Thanks in advance for your help. Happy holidays.
>
>Randall