Tom,

If I understand your comments on the Inno Setup Utility, one can mechanically generate a single file setup utility by building a 'setup' type ini file like the sample file you provided?

Thanks for your recommendation on InnoSetup!

Malcolm


Snipped ...

Here is a sample of a setup file in Inno that generates a self-extracting SETUP.EXE for a simple VFP project (one EXE, a doc file, and the VFP runtime):

>[Setup]
>Compression=bzip/9
>OutputDir=\\ITCORP2\D\PACKAGE\DBSpy
>OutputBaseFilename=setup
>AlwaysCreateUninstallIcon=Yes
>AppName=DB Spy
>AppVerName=DB Spy Version 1.0
>AppCopyright=Copyright © 2001 American Agrisurance Inc.
>DefaultDirName={pf}\DBSpy
>DefaultGroupName=AmAg Apps
>Uninstallable=Yes
>UninstallDisplayName=DB Spy 1.0
>UninstallFilesDir={app}\uninst
>MinVersion=4,3.51
>
>[Files]
>Source: "dbspy.exe"; DestDir: "{app}"
>Source: "DB Spy.doc"; DestDir: "{app}"
>Source: "C:\WINNT\system32\VFP6R.DLL"; DestDir: "{sys}"
>Source: "C:\WINNT\system32\VFP6RENU.DLL"; DestDir: "{sys}"
>
>[Icons]
>Name: "{group}\DB Spy"; Filename: "{app}\dbspy.exe"; WorkingDir: "{app}"
>
>Check out the Inno site at: http://www.jrsoftware.org/isinfo.htm