<div dir="ltr"><div>We've had this filepro sytem for years -- CentOS 5.10 and filePro 5.6.10R4</div><div> </div><div>We have an app written years ago that is basically a front end lookup to a main customer file</div><div>
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</div>
<div> </div><div>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....</div>
<div>Everything has worked out with no problems.....I only mention this because this is the only thing that's changed on this system...</div><div> </div><div>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'??</div>
<div>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'</div>
<div> </div><div>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....</div>
<div> </div><div>Thanks for any insight....pretty confused on this</div><div> </div><div>Scott</div><div>PDM</div></div>