Dan,

If it's only altered from another instance of VFP, why not just create a system table with one record and lock that record while the app has control of the config file. The other app would have to wait until it can get a lock on that record to know it's ok for it to use the config file.

>VFP 3.0
>I'm using VFP as a wrapper aroung a DOS app. There are 2 users that will be able to access this program in a network. Prior to running the app, I alter the configuration file and change the printer type based on the user. Unfortunately there is a considerable time lag between the time the CFG file is altered and when the app actually loads the file. What is the best way to prevent the other user from altering that file in that interim?