Article ID: 130664
Article Last Modified on 8/11/2005
The following table lists the sizes of files that could be included with
your setup routine.
<BR/><BR/>
Select this option if
Option Size your application...
-----------------------------------------------------------------------
Visual FoxPro 3.0 Runtime 3.5 MB Requires the Visual FoxPro Runtime
(Vfp300.esl) to execute.
Microsoft 5.0 Graph Runtime 2.2 MB Includes forms that use Graph 5.0
controls.
ODBC Drivers 3.5 MB Communicates with tables other than
Visual FoxPro .dbf files. When you
select this option, the ODBC
Drivers dialog box appears so that
you can select necessary drivers.
ODBC Drivers (Win32s) 4.3 MB Communicates with tables other than
Visual FoxPro .dbf files. When you
select this option, the ODBC
Drivers dialog box appears so that
you can select necessary drivers.
Win32S (1) 4.0 MB Is being distributed to users
running Windows version 3.11.
Visual FoxPro applications require
Win32s.
Windows 95 (1) 0.5 MB Is being distributed to users
running Windows 95.
Windows NT (1) 0.5 MB Is being distributed to users
running Windows NT.
(1) If you are distributing files other than Visual FoxPro applications,
such as a Help file, you don't need to select a platform option.
The sizes listed above represent the bytes used after the files have been
installed on a user's hard disk. When the user runs the setup these sizes
might be slightly exaggerated.
Column Description
------------------------------------------------------------------------
File The file name as it will be created on the user's computer.
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
Manager Item dialog box, so you can specify the 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 are installed in
the correct subdirectory if your users specify a name for
the application directory other than the default name. The
following example installs MYDATA.DBF 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 installs the icon in your application directory.
OLE If you select this option, the generated setup registers the
OLE control when it is installed on a user's computer. This
does not register a design-time license for the control on the
user's computer. It is a good idea to have your setup register
OLE controls to ensure that your user always uses the correct
version of the control.
Visual FoxPro allows an OLE control to be created or
instantiated only if the control and its license have been
purchased and installed on your computer. License information
is saved with the form or class. This allows distributed forms
to run successfully on users' computers. Users cannot modify
these forms in design-time unless they also purchase a
design-time license from the manufacturer of the control.
You may distribute visual class libraries that contain OLE
controls. New controls based on these visual classes can be
added to running forms. Users, however, may not modify these
visual classes, create controls based on them, or subclass
them.
OLE controls may be developed and distributed without charge
or licensing requirements. However, most are designed so that
they fail without a license. There are currently two types of
licenses for OLE controls, design-time and run-time. A
design-time license allows you to create new OLE controls. A
run-time license allows you to run a form that contains an OLE
control.
For more information about distributing applications with OLE
controls, please see the "Distributing OLE Applications" topic
in the Visual FoxPro Help file.
Keywords: kbhowto kbsetup KB130664