Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ACK!! The amazing failing RLOCK()
Message
From
26/10/1998 17:54:12
 
 
To
26/10/1998 17:17:33
Tim Hockin
Illinois State U - Residential Computing
Normal, Illinois, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00150675
Message ID:
00150695
Views:
12
Tim,

I can't really say, but *could* it be related to some maximum setting in the network software? I suppose your Net folks could tell you that.

You should also know that ISRLOCKED() only returns .T. if it is the application *ISSUING THE COMMAND* which has a lock on the record. In other words, you cannot use ISRLOCKED() to detect if someone *ELSE* has a lock on the record.

Good Luck,

Jim N

>looking at the RI code generated by Xcase (v4) - I have an RLOCK that is failing.
>
>It is in a loop for all records. After 496 records, rlock fails. I can not determine why. It is not ISRLOCKED()...each record is UNLOCKed at the end of each loop iteration.....
>
>I am stumped...why might an RLOCK() fail, and can I get more info as to why it returned .F. ????
>
>Help, please!
>Tim
Previous
Reply
Map
View

Click here to load this message in the networking platform