OK, that way it looks legal to me. It looks like the OS shows you an outdated version of the file. Sorry, I have no further ideas on how to solve this.

Hilmar.

>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
>
>HTH
>
>>Thou shalst not use reserved words for thy own objects. KEY is one. However, I am not sure if this is the cause of your troubles.
>>
>>Try renaming the table. Do your problems persist?
>>
>>How do you change the values? With REPLACE, or with an object that has a .ControlSource?
>>
>>Hilmar.
>>
>>>Hi,
>>>
>>>We have a VFP6 app that uses a KEY file for licensing purposes.
>>>The problem is that each time we change a value in the KEY file,
>>>the changes are not reflected to the app until the we run it
>>>(the app) a second time. The app is distributed as a standalone
>>>EXE so we can't figure out where the old values are coming from.
>>>
>>>To further elaborate, say that the KEY file has the printing
>>>feature turned ON. I run the EXE, the feature is ON. Now, I
>>>set the printing feature OFF. I run the EXE the first time and
>>>it is still ON but on the second and subsequent runs, it is OFF
>>>as it should be. If I then turn it back ON, the first run will
>>>show that it is still off but on subsequent runs, it is ON.
>>>
>>>The problem is aggravated when running on Windows NT. It takes
>>>three or four runs for the changes to activate.
>>>
>>>Any help will be greatly appreciated.
>>>
>>>Thanks,
>>>Arriyel