The loader app reads the ini file to determine what version of our app is installed and that determines which runtime is required. The loader app checks the date/time/size of the runtime files in:

\Program Files\Common Files\Microsoft Shared\VFP

That is where our app always stores them. (We look for corresponding files in the system32 folder and if they are there then we move them) If the runtime files are incorrect then the loader app calls the runtime excecutable which installs the correct runtime files. If the runtime executable is not on the system then it downloads it from our https site and runs it. Periodically, another VFP app will install to the system32 folder and we end up having to move the files out of there. There is a popular small business tax preparation software that is written in VFP and stores the runtimes in the system32 folder which can create a conflict. Some of our users have 4 or 5 business apps written in VFP. There are a lot of insurance rating programs written using VFP as well. license file that is encrypted and determines the license of our app as well when the app loads.

I recently found ProLib's Runtimes at:

ftp://ftp.prolib.de/public/

They have some install switches too.


>Tracy,
>
>How do you determine if the run time is out of date?
>
>I use a loader app, but i don't check run time versions. I'd like to add that funcationality.
>
>Thanks, j
>
>>We run a loader app always that calls our exe. The loader app verifies the runtime versions and also ocx's, etc. We have a separate runtime install that is called if the runtimes are out of date. The downloadable update includes the separate runtime app as well. You might want to include the runtimes in the downloadable update for awhile. Do you have a means of tracking the version your users are currently running? We pass a license file back and forth that notifies us of which version our users are running and which version they are licensed for.
>>
>>>We are preparing to update to Service Pack 1 for VFP; however, we are concerned that our users may run into issues with the "pre-release" of our application. We allow our users to download a pre-prelease version of our application. This started in early October. We are now preparing to send out final CD versions (is there ever really a final version?) using VFP9SP1. The problem is, our users will be downloading updates from our website that were compiled in SP1 and running the EXE using the original VFP9 runtime UNTIL they get their CD and install the SP1 runtimes.
>>>
>>>My question is, will this work? Will they be able to run a VFP9SP1 EXE using VFP9 runtime???