Record Is Being Updated - Access Denied

[Kenneth Brody]

On 6/13/2013 2:07 PM, Dennis Malen wrote:
> Ken,
>
> The following are comments concerning your three suggestions in your email
> below:
>
> (1) explicitly unlocking the file.  KEN, DO YOU MEAN TO ACCESS "? - filePro
> Directory" AND UNLOCK THE FILE? This does not work for me.

No.  I mean to have the process that put a lock on the record to remove that 
lock.

> (2), closing the file, which removes all locks - KEN, HOW DO YOU CLOSE THE
> FILE? I KNOW HOW TO DO SO WITH A PROCESSING COMMAND. IS THAT WHAT YOU ARE
> REFERRING TO?

I was talking in general terms, not in filePro-specific terms.  If a process 
has a lock on a file, and closes that file, the locks are cleared.  In terms 
of filePro, if the locked record is in a lookup file, then "CLOSE 
lookupname" will have that effect.  However, since we don't know what 
process has the record locked, I can't give anything more specific.

> (3) exiting (or being killed) which closes all open files - KEN, DO YOU MEAN
> FOR EACH USER TO EXIT THE FILE. IF SO, THAT IS MY PROBLEM AS EVERYONE IS
> LOGGED OFF WHICH IS CONFIORMED BY THE "WHO" COMMAND AND THE RECORD IS STILL
> LOCKED.

No, I mean for the process that has the record locked to exit.  However, we 
still don't know what process has the lock.

Just because every is logged off (which isn't exactly true, since you're 
logged in) doesn't mean that every filePro process has exited.  It could be 
a process run via "cron".  It could be a background process run with 
"nohup".  It could be some "hung" process left after the user's computer 
crashed and didn't end the processes that were running on that tty.  It 
could be any number of things.  Until you run "showlock" and find the 
process, we can't give anything more specific.

[...]

-- 
Kenneth Brody