The wizard lists your files in a grid. You can change the settings for any file by clicking the item that you want to change. The following table describes the settings displayed in each column.
| Column | Description |
| File | Specifies the file name as it will be created on the user's machine. |
| Target Dir | The file can be installed on the user's machine in the Application directory, Windows directory, or Windows System directory. |
| PM Item | If you select this option, the wizard displays the Program Group Menu Item dialog box so you can specify program item properties: description, command line, and icon.
In the command line, you can use an embedded %s sequence to replace the application directory. The "s" must be lowercase. Use the %s sequence when you install files in application subdirectories. This ensures that files will be installed in the correct subdirectory in case your users specify a name for the application directory other than the default name. In the following example, Mydata.dbf is installed in the MAINDATA subdirectory of the application directory: %s\Maindata\Mydata.dbf If you specify an icon that is outside your source tree, the setup routine will install the icon in your application directory. |
| ActiveX | If you select this option, the installation process will register ActiveX controls during setup on a user's machine. This does not register a design-time license for the control on the user's machine.
It is a good idea to have your setup register ActiveX controls to ensure that your user always uses the correct version of the control. |
Visual FoxPro allows an ActiveX control to be created or instantiated only if the control and its license have been purchased and installed on your machine. License information is saved with the form or class that allows distributed forms to run successfully on users' machines. Users will not be able to modify these forms at design time unless they also purchase a design-time license from the control's vendor.
You may distribute visual class libraries that contain ActiveX controls. New controls based on these visual classes may be added to running forms. Users may not modify these visual classes, create controls based on them, or subclass them.
ActiveX controls may be developed and distributed without charge or licensing requirements. However, most will be designed so that they fail without a license. There are currently two types of licenses for ActiveX controls: design-time and run-time. A design-time license allows you to create new ActiveX controls. A run-time license allows you to run a form that contains an ActiveX control.
For more information about distributing applications with ActiveX controls, see "Including COM Components," in Chapter 25, Building an Application for Distribution, in the Programmer's Guide.