Installing the executable application and supporting files
When you install your application on a user’s machine,
make sure you include any supporting files, such as dynamic libraries,
resources such as BMP and ICO files, online Help files, and initialization
files.
Deploying ActiveX controls
If your application uses ActiveX controls (also called OLE
custom controls or OCXs), you must:
- Deploy
the ActiveX control files with your application - Make sure each ActiveX control is registered
- Make sure required files are in the target machine’s
system directory
Registering ActiveX controls
ActiveX controls provided with PowerBuilder are all self-registering–they register
themselves when they are used. If you use an ActiveX control that
is not self-registering, you need to register it manually on each
user’s machine. To find out whether a control is self-registering,
see the documentation provided with the ActiveX control.
To register an ActiveX control:
-
Run the regsvr32.exe command with the ActiveX
control’s filename as an argument. For example, the following
command registers an ActiveX control called ABCDE:1regsvr32.exe abcde32.ocx
Troubleshooting ActiveX control registration If you have trouble registering an ActiveX control, make sure
that the same versions of the following DLLs are available on both
the development and target machines: MFC40.DLL, MFC43.DLL, OLEPRO32.DLL, MSVCIRT.DLL,
MSVCRT.DLL, MSVCRT40.DLL, STDOLE2.TLB, CTL3D32.DLL, WININET.DLL
If the versions do not match in either size or date, copy
them from the development machine to the target machine and register
MFC40.DLL and OLEPRO32.DLL on the target machine. There are different
versions of CTL3D32.DLL for Windows 95, Windows 98, and Windows
NT.
Required files
Depending on the development and deployment platforms and
the ActiveX controls you are deploying, you may need to copy additional
DLLs or license files to the WINDOWS or WINNT system directories
on the target machine.
For more information, see the documentation
provided with the ActiveX control. You may also want to look in
the Technical Information Library on the Sybase website.
Creating registry information for OLE automation
objects
If your application includes user objects that are used for
OLE inbound automation, you must update the user’s registry
with information about the server. The Automation Server Project
wizard sets up a project which helps you to generate a globally
unique identifier (GUID), a registration (REG) file, and a type
library (TLB) file. The Automation Server project wizard is available
on the Project page of the New dialog box.
For more information, see “Deploying an application
that uses the automation server “.