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:
00173377
Views:
33
Brenda,
George has a good point about Client 32 - he knows a great deal more than I. However, I DO know that if the network is holding a lock after an app is closed (usually abnormally for this to happen) you cannot release the lock by loading the app again - even if the same user loads it. The lock must be released by the network. Ask your Network Admin. what the default time to release a lock is. He may have it set to 'never'.

>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
Barbara Paltiel, Paltiel Inc.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform