Record Locking Not Working

[Kenneth Brody]

On 4/23/2014 3:46 PM, Del wrote:
> To my surprise last week I noticed that I can get into update mode on the same record from two different sessions at the same time.
> This only happens in my Windows 7 Pro 64 bit system running filePro 5.0.11.
> I start up two different filePro sessions on my Windows monitor, and they can update the same record at the same time.
> I make a change in one and save it, then save the other and it wipes out the change made by the first.
> On my SCO Unix 5 system, trying to do this results in a message that says the record is being updated, access denied.
> It should work that way in Windows too.
> I also found that if I am in update mode on a record and run an output process from another session, that process will update the record I am on even while I am in update mode.  On my Unix system, the output process will wait for the record to be unlocked.
> So it appears that record locking does not work on my Windows system, and I am wondering if anybody else has this problem or if anyone has an idea of how or why it could happen?

Unless the file is read-only (or you have told filePro to run in read-only 
mode), and you have set PFREADONLYWARNING=OFF, then I know of no reason why 
filePro wouldn't lock the record when entering update mode.  (Well, other 
than using an ancient single-user MS-DOS version, that is.)

If you update the record, make changes, and save it, do those changes "stick"?

Does this happen on any file, or just one particular file, or perhaps even 
just one particular file via one particular prc table?

-- 
Kenneth Brody