Lynda

This is an example of an inno setup up script. It is pretty staight forward and can be used in your situation.


I have all the files,tables, etc I want to distribute in a folder called c:\dist_fuba

This installation registers one ocx file which is in c:\dist_ocx folder. You can register others if needed by using the same syntax.

The license file is locate in c:\license

The rest of the files you will need for VFP9 runtime.

This installation will not create icons etc as the Icons on already on the users computer. See the inno example if you want to create desktop icon.

You can do a lot more with Inno, but this will get you going.

[Setup]
AppName=FUBA APPLICATIONS
AppVerName=FUBA
AppPublisher=Gaylen Jungling & Associates
DefaultDirName=C:\fubamenu
DisableDirPage=yes
DefaultGroupName= FUBA Applications
LicenseFile=c:\license\license1.txt


[Files]
Source: "C:\dist_fuba\*.*"; DestDir: "{app}"
Source: "C:\dist_vfp_runtime\gdiplus.dll"; DestDir: "{sys}"; Flags: uninsneveruninstall onlyifdoesntexist
Source: "C:\dist_vfp_runtime\msvcr71.dll"; DestDir: "{sys}"; Flags: uninsneveruninstall onlyifdoesntexist
Source: "C:\dist_vfp_runtime\msvcp71.dll"; DestDir: "{sys}"; Flags: uninsneveruninstall onlyifdoesntexist
Source: "C:\Program Files\Common Files\Microsoft Shared\VFP\vfp9t.dll"; DestDir: "{sys}"
Source: "C:\Program Files\Common Files\Microsoft Shared\VFP\vfp9r.dll"; DestDir: "{sys}"
Source: "C:\Program Files\Common Files\Microsoft Shared\VFP\vfp9renu.dll"; DestDir: "{sys}"
Source: "C:\dist_ocx\mscomctl.ocx"; DestDir: "{sys}"; Flags: regserver sharedfile  restartreplace

Hope this helps
Gaylen


>I need a simple, straightforward, error-free way to install a new application. It should install and/or register only those files that are truly necessary into logical, predictable folders. While that would seem an obvious objective, I have never been able to accomplish it with InstallShield. This time, I’m planning to use InnoSetup. There are several threads here and on Fox Wiki about setups but much of the information is contradictory or applies to specific, and often older, operating systems.
>
>What runtime files constitute the bare minimum? This is an English-language VFP 9 EXE running on Windows XP workstations. Some users will access it via Windows Remote Desktop. The app should reside on the workstations while the data is in SQL 2005 on a Windows SBS 2003 server. The runtime files list obviously includes msvcr71.dll, vfp9r.dll and vfp9renu.dll. Is vfp9t.dll useful? Is it true that gdiplus is redundant for Windows XP?
>
>Historically, VFP runtime files have been “splattered” across the disk—some in the system directory, some in a shared directory and some in the application directory. Since there will be a single VFP application I’d like to place all of the runtime files in the application folder. One contributor on Fox Wiki indicates that none of the files needs to be registered if they are located in the folder with the application. If that proves to be correct, it should greatly reduce installation and maintenance problems, a major objective.
>
>The application uses an older version of Amyuni’s PDF Converter (2.06, one of the last with royalty-free distribution included.) I haven’t been able to install it on the server (seems to be a ‘policy’ issue) so it will have to go on the workstations. Is there a good reason why it should not be put in the application directory too?
>
>While I maintain the application code, all of my clients have IT staff to maintain the OS and hardware. Inevitably, they must also install the application occasionally and troubleshoot installation problems. Most of these IT departments do not welcome VFP apps because they find them “difficult to maintain.” I’d like to make life easier for them and for me. Your thoughts on this somewhat unconventional approach are appreciated.