|
Home > Archive > FoxPro Help and Support > April 2006 > How to tell which user has record locked
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to tell which user has record locked
|
|
| Pete Fisher 2006-04-05, 9:35 am |
| An VFP6 application with a table shared by many users reports the same
record persistently locked. Generally this has been avoided until now by
using a timer to force an UNLOCK if a user leaves the application
running in edit mode.
This time I can not trace any machine (of dozens) that is currently
running the application.
Could a server error result in this behaviour? One machine was found to
be reporting an 'unable to read file' error, but rebooting has not
cleared the lock.
Any way to find out which user has the record locked?
The table is on a Novell server - unfortunately I am not the
administrator, but it would help if I knew just what to ask the sysadmin
to resolve the problem.
--
+-----------------------------------------------------------------+
| Pete Fisher at Home: Peter@ps-fisher.demon.co.uk |
+-----------------------------------------------------------------+
| |
| Dan Freeman 2006-04-05, 11:37 am |
| There is a Novell utility your sysadmin can use to determine who has that
lock. Just ask him/her "who has this locked?" <s> They do this stuff all the
time.
Dan
Pete Fisher wrote:
> An VFP6 application with a table shared by many users reports the same
> record persistently locked. Generally this has been avoided until now
> by using a timer to force an UNLOCK if a user leaves the application
> running in edit mode.
>
> This time I can not trace any machine (of dozens) that is currently
> running the application.
>
> Could a server error result in this behaviour? One machine was found
> to be reporting an 'unable to read file' error, but rebooting has not
> cleared the lock.
>
> Any way to find out which user has the record locked?
>
> The table is on a Novell server - unfortunately I am not the
> administrator, but it would help if I knew just what to ask the
> sysadmin to resolve the problem.
>
>
>
>
> +-----------------------------------------------------------------+
> +-----------------------------------------------------------------+
|
|
|
|
|