Thanks for the suggestion. I'll try it soon and let you know. I have
assumed that because of the locks and ghost users I wouldn't be able to
connect in single user mode.
=======================================
At 07:37 AM 7/31/2001 -0500, you wrote:
>Did you have to reload the database? I have found that connecting to the
>database in single user mode usually will clear the ghost users/locks.
>
>Sometimes I have had to restart the server, but then a single user mode
>connect ion will finish clearing up.
>
>-- Dennis McGrath
>mailto:[EMAIL PROTECTED]
>
>-- Tools for R:BASE programmers
>http://www.enteract.com/~mcgrath/dennis
>
>-- Full time consultant with SQL Resources
>mailto:[EMAIL PROTECTED]
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>Behalf Of Bernie Corrigan
>Sent: Tuesday, July 31, 2001 2:32 AM
>To: [EMAIL PROTECTED]
>Subject: RE: How to find a user with a cursor lock on a table
>
>
>At 11:55 PM 7/18/2001 -0400, you wrote:
>>If you have access to the server (physically or via software) you can check
>>files locked by user. How you do so depends on the server OS you are
>>running. Once there you can "delete" the connection. If you post that you
>>can be steered to the correct place.
>
>IMHO this is not always the case. I am currently dealing with a Win 6.5
>database which picks up ghost users regularly. These ghost users, who
>sometimes have locks, are not visible from the server, Novell 4.11. The
>server shows no file locks whatsoever on the database files yet RBase thinks
>they are there. We are able to get rid of them for a while by rebooting the
>server and then reloading the database; however, after a while they start
>showing up again. I have no idea what is causing them and we are currently
>in the process of trying to find the cause.
>
>
>
>
>
