Only if the backend database allows for it. Oracle does with a SELECT ... FOR UPDATE clause. However, I think this is a very bad idea on SQL databases since the client is partially or totally disconnected during the edit process. If the client goes away without posting back to the database, the records could remain locked until a DBA manually unlocks them.

At least with native DBFs, when the app closes the table, the locks are released.

>Mark,
>
>How about locking particular record(s) just like RLOCK() when manipulating DBFs?