I was getting that same error message last week in an app that was recently functionally converted to VFP from FP/DOS 2.6. During the VFP version testing phase, we are running both versions against the same set of DBF's. The error was caused by a SHOW GETS command that was refreshing a form with @ SAY's that reference database fields. SHOW GETS locks any records referenced by @ SAY's. So, if the database is at EOF() the SHOW GETS is locking the dummy record at eof. If two users are at eof and displaying (and locking) this blank dummy record, FP/DOS does not care (the code has been working OK for years). However, VFP does not like it when two users try to lock the dummy record and it issues the "Record in use by another user." error.

The solution was to put the database fields into vars and put the vars in the @ SAY's.

Hope this helps.

>This is a problem that I run into occassionaly and it's happening right now.
>
>In my production reservation system, any user which tries to update a field in the UNITS record will get the error "Record in use by another user." I've tried this on four different terminals.
>
>It doesn't matter which record in the table you try to change; you still get the error.
>
>The system is using local tables on a Novell file server. Approximately 30 terminals have this table open.
>
>The program is based on Visual FoxExpress version 5.0. The UNITS form has its own data session using optimistic table buffering.
>
>If I use EDIT/BROWSE from the command prompt I can change records in the UNITS table without any problem.
>
>Presumably one terminal has some kind of lock on this table which is hanging things up.
>
>Any ideas what the problem might be?
>
>Peter Robinson