When you run an installer program, the application files that the installer program processes should be in directories that represent the directory structure you want the Setup program to create when it installs your application. The Directories option on the Product Builder menu lets you create that installation directory structure and copy files from the project directories to the installation directories.
When you select the Directories option on the Product Builder menu, VPM Enterprise displays the Product Builder Directories dialog.
The installation directory structure for most applications will consist of:
· A home directory that contains the .EXE file, the Help file and, perhaps, a CONFIG.FPW.
· A \DATA directory to hold the tables, indexes and memo files.
· A \REPORTS directory to hold the report files.
Project Home + “I”: This is the installation directory structure that VPM Enterprise automatically suggests. VPM Enterprise creates the name of the home installation directory by appending an ‘I” to the name of the project home directory. VPM Enterprise enters this directory structure on the Product Builder Directories dialog.
Change Directory Structure: You can, of course, change the installation directory structure to whatever structure you want. If you want only one directory, enter the same directory name in the Home, Tables and Reports directories fields.
Add Directories: If you need additional installation directories for your application, the Product Builder Directories dialog provides the space to enter the paths and names of up to three additional directories.
Create/Copy: When the Product Builder Directories dialog displays the installation directory structure you want, click the Create/Copy button.
VPM Enterprise creates the installation directories and then displays the Copy Files dialog consecutively for the Home, Reports and Data directories. The Copy files dialog is a mover form that displays the files in a project directory in a list box on the left. You move your selected files to the list box on the right.
The Copy Files dialog lets you choose the application files to copy:
· Home: From the project home directory to the installation home directory.
· Reports: From the project reports directory to the installation reports directory.
· Data: From the project data directory to the installation data directory.
You can select the source files individually or you can click the right-double-arrow button to copy all source files to the destination installation directory.
The Copy Files dialog for copying files from the project’s Home directory to the application’s Home directory appears first.
The files that are normally distributed in the Home directory of a VPM Enterprise application are already selected. Select any other files you want and click OK.
The Copy Files dialog for copying files from the project’s Reports directory to the application’s Reports directory appears next.
Select your report files and click OK. You normally will select all report files.
Tip: If you distibute the Main Menu report SVSAFMainMenu.FRX, you will need to distribute the menu files S<Prefix>FMAN.MNX/MNT.
Tip: Only report files that are not built into an application should be distributed. A report file is built into an application if it is in the Project Manager and is not marked as excluded.
The Copy Files dialog for copying files from the project’s Data directory to the application’s Data directory appears next.
Select the data files you want and click OK.
Files to Include on the Distribution Disks
The following files should be distributed with a VPM Enterprise application:
· Project Home Directory: Copy the following files to the installation Home directory: the .EXE or .APP file, SVPMApplicationDefinition.APD, SVPMApplicationDefinition.FPT, S<Prefix>HELP.HLP or S<Prefix>HELP.CHM, MAIN.INI and MAINTEMP.INI.
· Project Reports Directory: Copy the system report files that you're including in the application and your report files to the installation Reports directory.
· Project Data Directory: Copy all the system files (i.e., files with names that begin with “SDATA” and “SVPM”) plus all of your data files that should be part of the application to the installation Tables directory. (You don’t need to copy files named SVPMAdminTools1, SVPMCalledObjects, SVPMMenus and SVPMFoxUser.)
· FoxPro Files: If you are distributing an .EXE and your installation routine installs the Visual FoxPro runtime library files, you don’t need to include the Visual FoxPro runtime .dll files. Otherwise, you need to include the following files from your \Program Files\Common Files\Microsoft Shared\VFP directory in your installation home directory:
VFP 9.0: VFP9R.DLL and VFP9RENU.DLL (locale .DLL)
If you have prepared your application for a language other than English, include the appropriate locale .DLL for that language.
· CONFIG.FPW: If you have created a CONFIG.FPW to control your application’s environment at startup, copy the CONFIG.FPW to the installation home directory.