>>>>>>I introduced locking because users were complaining that occasionally when 2 of them were
>>>>>>inserting at the same time that one will suddenly start editing the other's record.
>>>>>>In the above, I changed to table locking but get the same error, the only difference is
>>>>>>that I do not see Bill's record in Sue's session.
>>>Sorry then. I don't know of a way to get another buffered table's (in buffer) record unless
>>>I can switch to its workarea. Without being able to reproduce no idea.
>>
>>George, I _have_ seen this before, and managed to trim it down to a very simple repro. Unfortunately,
>>I can't figure out what that was. Can you post code that will show the behavior? It's been ticking me
>>off since VFP3.


I have had similar troubles and have even seen some data shifting in some data in records. Depending on how often you have an instance where two users can actually be in the same account, what I did to avoid the whole thing is, in my password table which contains all our users, passwords, name, security rights, etc. I added a column for our account number, then on the access points of going into an account, I seek the current logged in user in the password table and log that account number. The function logs the number when they enter an account and blanks the field when they leave one, or replaces it with the new acct number they go into. Upon entering the account a check is made on the password file to see if a user is already in that account and if so, they have the ability to notify them by the name given in the messagebox and ask them to let them in, or wait and try again later. I was also able to create a monitoring system from this where I access the password file and can see all users logged in, what accounts they are in, and how many minutes they have been in them. Tells me who is not working. Of course if you have few records and more likely to need two people in a record at once, you may not want to take an alternative like this.