records not locking?

[Del]

Don't know anything about CentOS.
However, I have been dealing with filePro for many years, and always understood 
two people could not update the same record at the same time (using dclerk or 
rclerk).
After reading your post, I tried it here on a Windows 7 based system, and was a 
little flabbergasted to find that the system allowed me to get into update mode 
on the same record from two different sessions.
However, when I tried it on my Unix system, an attempt to update a record that 
was already being updated on another session gave me the message, "Record Is 
Being Updated - Access Denied".
This difference between the Windows based system the the Unix based one is very 
surprising (and disturbing!).

Del Neroni

-----Original Message----- 
From: scooter6 at gmail.com
Sent: Wednesday, April 16, 2014 8:04 AM
To: filepro-list at lists.celestial.com
Subject: records not locking?

We've had this filepro sytem for years -- CentOS 5.10 and filePro 5.6.10R4

We have an app written years ago that is basically a front end lookup to a
main customer file
It used to be if someone has a record pulled up from this main file, and
someone else attempted to access it, you would see at the bottom something
stating watiing for record to be unlocked or something like that, don't
remember the exact verbiage

Some of you might remember I recently had to replace the CentOS RAID and
left the filePro RAID in tact when we had a root kit virus.....so I simply
swapped the 2 OS drives and configured what I needed to user wise,
etc.....by taking the /etc/passwd files, etc from the old OS and on to the
new OS drives....
Everything has worked out with no problems.....I only mention this because
this is the only thing that's changed on this system...

Yesterday, one of my operations people informed me that two people could
have the same record pulled up at one time and update it 'at will'??
Now the program used to access the main customer file is just a filePro
file that does a lot of lookups to display the data from the main customer
file - and I checked input processing and made sure all the lookups are
'protected'

Any idea what would cause them no longer seeing the 'waiting for record to
be unlocked' message as before?  Very strange.....this has never been the
case in the 15 yrs we've had this program built, etc....

Thanks for any insight....pretty confused on this

Scott
PDM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.celestial.com/pipermail/filepro-list/attachments/20140416/ad21e007/attachment.html
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list