I always thought cacheing was designed to work in this way...
Eg yes, it keeps your file in memory until it need to write it out to disk but it also keeps your changes in memory as well so as long as you are reading from the same machine that is making the changes the cache will be up to date and you will see current values.

It sounds more to me as if VFP is not emptying it's buffers so the OS doesn't know that VFP has made changes. therefore if you look at the file outside of VFP it still looks like the old version.

You could try doing a FLUSH after making the changes
Also have a look at the following
http://fox.wikis.com/wc.dll?Wiki~SYS(1104)~VFP

HTH
Will


>In the my test, I would have two key files (named differently) with one as
>the CURRENT.KEY file. I would run the app and check if it works. I then
>close the app and rename the current key file to say OLD.KEY then rename
>the other key file as my CURRENT.KEY file. I would then run the app again
>and check if the changes are working. The changes are not reflected until
>the second and subsequent runs of the app. I could do it the other way
>with the same results.
>It could be a caching problem since the KEY files are very small and may
>be kept in the cache longer (does that make sense?).
>
>Thanks
>
>>Sounds like a caching problem such that the network is not writing out the changes until the app is restarted or the network client is not re-reading the file because it thinks it has a current version (I am just guessing here). If you do the change via the app (or the licensing software) and then immediately go to the network and view the changes with an editor (I am assuming that this is a text file), do you see the changes made right away or are you looking at old values? I am not a "caching" guru but just some thoughts.
>>
>>Alber
>>
>>>The KEY file is a separate file that has the '.KEY' extension.
>>>It is an ASCII text file that is created by the licensing
>>>software. The app reads the KEY file for specific flags and
>>>stores the values into memory variables. Any tampering with
>>>the KEY file themselves can will invalidate it and the client
>>>can loose their license to use the app.
>>>
>>>It looks some thing like this:
>>>
>>>; Tranquility Base Validation Key
>>>;
>>>; ***WARNING***WARNING***WARNING***WARNING***WARNING***
>>>; Tampering with this key will result in program malfunction.
>>>; Keys that have been tampered with in any way WILL NOT
>>>; be replaced. You have been warned!
>>>;
>>>;Company
>>>#gcCompName
>>>%My Computer Company, Inc.
>>>3312678593345932711924424884781748111242532814997363907293985378884275
>>>0593987314174811234517481154861748191137174818133917481395981748113596
>>>8748195669174816869117481216921748184741174814654617481237841748138136
>>>1548125373174814438217481872491748185658174815443117481524450948155195
>>>17045678981748189939
>>>