>>Hey where there's a will there is a way.... First off "launcher" should only be responsible for launching right? right. hmmmm. So it's asy enough to spit a dummy text file out that would be the KISS indicator to install dll's in addition to copy an exe. When the launcher detects that text file wouldn't it be best to set it up to call WSH(?) to start the installer and then release itself. IOW... cant we just modify our launcher programs to launch the installer and end, therefore eliminating the hassle of a VFP app running when installer kicks off to update runtimes?
>
>Sounds like we are onto something here.

Yep you are, and here's a start. Remember that the WSH can also place a short cut in the Startup group. The following code could be modified to: Check for the presence of a text file indicating that setup has to be run and compare its date with a local copy of the same. If the copy on the net was later than the local one, it could copy the new one, create a shortcut in the startup group, run the new setup. When the machine re-booted the new version would be installed. You'd simply check for the presence of the shortcut in Startup and delete it.

' Launcher.vbs
' George Tasker - 6/6/2000

Dim oFSO, oLocal, oRemote, cExe, cLocal, cRemote, oShell
cExe = "myexe.exe"
cLocal = "C:\vfpLocal\"
cRemote = "F:\sourcedir\"
Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oShell = CreateObject("WScript.Shell")
Set oRemote = oFSO.GetFile(cRemote & cExe)
If Not oFSO.FileExists(cLocal & cExe) Then
  oRemote.Copy cLocal
Else
  Set oLocal = oFSO.GetFile(cLocal & cExe)
  If oRemote.DateLastModified > oLocal.DateLastModified Then
    oRemote.Copy cLocal
  End if
End if
oShell.Run(cLocal & cExe)
' End Launcher.vbs

Waddya think of that?