Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Not RLOCK()
Message
From
19/12/1998 12:40:01
Raymond Humphrys
Michigan Department of Community Health
Bath, Michigan, United States
 
 
To
19/12/1998 12:29:33
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Miscellaneous
Thread ID:
00169129
Message ID:
00169138
Views:
18
Maybe I don't understand how RLOCK works, but I thought that it kept everyone off the record except the first person. That once someone was on a record no one could even look except AFTER the original person moved off the locked record. I have a situation where 1 person can edit and everyone else can only see read-only controls until the original person is done.

>>If a record on a Network is brought up in a READONLY state ( all controls are READONLY), and there is a control to switch them to a READ/WRITE state is there a way to determine if someone else is using the record and prevent the switching to READ/WRITE?
>>Simply, everyone can look at any time, but only one can READ/WRITE on the record at a time.
>>
>>thanks
>Why Not RLOCK()
>Cetin
Some days it's not worth chewing through the leather straps ...
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform