Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Can abnormal termination keep an RLOCK()?
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00172898
Message ID:
00173095
Views:
31
Network is Novell Netware, client 32. I have no network rights. The single application is mine, but the server and network are used by hundreds of other apps. What are my options when this happens?

Do you know how RLOCK() are kept? Do you think that if the same person who had the RLOCK() and crashed, then came back through the code that VFP would let them do the RLOCK(). Of course what I really want is for them to RLOCK() successfully, so they will then get to the UNLOCK.

Thanks - Brenda

>Brenda,
>What kind of network does the client have? I know that locks can be kept on Novell networks if your EXE crashes. How long they are kept depends on a network setting. I think the default is 20 minutes, but it can be changed over a wide range. NT seems to have a similar situation according to one client.

>HTH
>Barbara

>>Debugging a client problem. Client keeps getting an "file in use" message. Client is on a network but the only current user. Tracked the message down to a RLOCK() on a table that only has 1 record (holds the next sequential number).
>>
>>1) can abnormal termination keep an RLOCK()
>>2) can a previous FLOCK() or RLOCK() from the same client prevent an RLOCK(). Can a person lock themselves out?
>>
>>Thanks - Brenda
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform