>As part of our application startup code, we would like to verify that any system files (ActiveX's, DLL's, Fox runtime files, etc.) our application is dependent on are at the latest version based on an updated list of file names and version numbers downloaded from our web site.
>
>1. Any suggestions on how we can detect that a file 'is in use' before we try to overwrite it (so we can set a flag notifying the user that a reboot is necessary)
>
>2. Is there an API function and/or WSH method that would allow us to queue(?) files for overwrite following a system reboot?
>
>3. Are there any reasons we should avoid this strategy for keeping our applications up to date? One fear is that certain sets of files may need to be updated as a group ('transaction') so that if we individually upgrade interdependent files, we may crash the operating system?
>
>4. Anyone doing anything similar?
>
>Any feedback appreciated!
>
>Regards,
>Malcolm

Hi Malcolm,

Using the Windows Installer (WI) technology is a good way to accomplish what you want to do. Although Microsoft makes WI available for free, it's not that easy to use by itself. VFP 7.0 ships with InstallShield Express, which makes creating WI installations considerably easier. For more powerful installations, you can look into the full version of InstallShield for Windows Installer, or Wise for Windows Installer (http://www.wisesolutions.com). I use Wise for Windows Installer, and I really like it.