>>Finally, one thing that used to be true years ago with xBASE was that, in a multi-user environment, the only time you could be guaranteed to be accessing current data was after successfully obtaining the appropriate lock - either RLOCK() or FLOCK(). AFAIK this is still the case. If so, with your current design you can't guarantee that the second station can view the first one's updates because the second one cannot get an RLOCK() on the necessary row. One possible workaround would be to use 2 tables:
>>
>>- table LOCKS has only 1 column, a primary key. Its sole purpose is to hold locks.
>>
>>- table LOCKDATA has the same PKey column, plus other info columns as needed e.g. user name, computer name etc.
>>
>
>Yes, that is where I have reached in my thinking. However, I have been able to duplicate the problem in the framework directly and I believe the framework developers are looking into it. Hopefully they will come up with a suitable solution soon. For now, I am just reporting that the record has been locked, not by whom.
>
>Thanks for your time and suggestions!

You're welcome.

Just out of interest, which framework is it?