Your easiest option may be to have a static web page with a link to the file to be downloaded. Include on the page, download instruction so they know where to download the file to [i.e., the directory where they installed the app]. This file would be the new encoded date file. Access to this page could be secured (userid and password required to access it).

Unless you are absolutely sure everyone installs the app in exactly the same directory that you dictate, finding the original encoded file could be a bear. You can darn sure bet their app directory won't be in any search path to make your locating any easier.

>Hi Jeff.
>
>>>Maybe I don't understand what you want, but if I do I don't think you have a prayer of getting this done tomorrow.
>
>ROF,L. I don't need to have the program completed by tomorrow. All I need are some options to present. I need to show the group that I can have this implemented within the next 6 months or so. The Application that uses the expiration date ships some time within the next week. It will not expire for a year.
>
>>>1.Does your local Fox app write this file to the pc?
>
>The file is a part of the installation. It is just a little text file that contains an encoded date.
>
>>>2.How do you update now?
>
>I don't. I need to be able to update it in the future.
>
>>>3.What is the file format?
>
>Ascii Text
>
>>>4.What do you use to decode now?
>
>I have a small .prg to create the encoded date. I have another function in the application that decodes the date and determines whether or not the app has expired.
>
>Marcia