>>We have a file that is used by all users but has to be updated ONLY by one application running unattended 24/7.
>>The app that updates the file has a flock() on the file. After starting the app we can no longer USE the file in VFP8 - we get "Attempting to lock... Press Esc to cancel"
>>But... we can USE it in VFP7!!!
>>We tested the following:
>>-Open VFP8
>>-In the command window USE and FLOCK() a file.
>>-Open another VFP8 session; USE the file - "Attempting to lock... Press Esc to cancel"
>>-Open VFP7; USE the file - no problem.
>>
>>Do you all see the same behaviour?
>
>See Re: Locking problem in 8 Thread #748662 Message #748709

Thanks Sergei.
It looks like we can't use this new feature if we need to have a file permanently locked. It is true, we could leave it unlocked, and attempt to always have NOUPDATE in all other applications - that is easier said than done. But the main problem is that if we leave it unlocked the file could still be changed in an interactive session, by accident.
For now we just put the tablevalidate = 0 in all config files.
BTW, I see this as a critical change that should've been mentioned/explained in the readme.