Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Network record conflict - Record is in use by another us
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00466139
Message ID:
00466189
Views:
13
>I test for network conflicts on data entry forms by running two simultaneous EXEs for User #1 and User #2.
>
>User #1 runs a form.
>User #1 presses Edit button and starts editing record.
>User #2 runs same form.
>User #2 presses Edit button and gets my msg - Try later. Record in use.
>That works. But...
>
>User #2 moves to previous record and comes back to same record User #1 is still editing.
>User #2 presses Edit button and gets system msg - Record is in use by another user.
>
>Why does this happen? And how can I fix it?

Check the error number returned by the two errors - there's more than one error related to 'record is in use' related to the buffer more and TABLEUPDATE() status - I've seen this where the view and underlying table are both buffered; the record was TABLEUPDATED() in the view, but not in the underlying table.

>
>I have ON ERROR trap where I test RLOCK() for .T. or .F. to display my msg. The first time User #2 pressed Edit button, RLOCK() was .F. and got my msg, but after User #2 moved the record pointer and returned to the original record RLOCK() was .T. and didn't get my msg, but got the system msg instead. I read that moving the record pointer can UNLOCK the record, but if User #1 is still editing the record, how can that happen?
>
>Thanks for the help.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform