Even after installing either SuitePro or a standalone ActiveX component on a development machine the necessary configurations must be registered prior to using the components.Ĭomponent registration on the development machine can be done using the Registrator tool included in the installation package. It is not enough to just copy component files to the target location to be able to use it, they must be registered and license included (described in the next section). Also three configurations may be installed in order to cover all possible use cases.Ĭomponents may be installed to any location that is at least read-only accessible for all potential users of the installed components.It is important to install 32-bit Unicode components even if they are not used as Windows OS requires all 64-bit COM objects to have corresponding 32-bit components installed. C# application with 圆4 or An圜PU TargetCPU, 64-bit Microsoft Office application or 64-bit C++ application with Unicode character set enabled. Using both 32-bit and 64-bit Unicode components if your application is a 64-bit application, e.g.C# application with x86 TargetCPU, 32-bit Microsoft Office application or 32-bit C++ application with Unicode character set enabled Installing 32-bit Unicode components only if your application does support Unicode, e.g.Visual Basic 6 application or 32-bit C++ application with Multi-Byte character set enabled. Installing 32-bit ANSI components only if your application does not support Unicode, e.g.It is important to choose the correct configuration that is compatible with your host application as Windows does not allow mixing the bitness of modules in one address space old programming languages do not support Unicode character set. Choosing the correct component configurationĬhoosing The Correct Component ConfigurationĮach Codejock ActiveX component comes in 3 configurations:Ĭomponent file names reflect its configuration, e.g.:.

This article explains the following related concerns: It is assumed that a developer is familiar with ActiveX concepts and best practices related to a programming language of his choice. The way to work with ActiveX components and related language dependent concerns are beyond this article as it is unique to each programming language. The controls can be used from any development environment and with any programming language that supports ActiveX technology. One component (.OCX) file exposes a set of classes and interfaces necessary for using controls it provides.

OCX files that must be copied and registered on the target computer where they will be used. NETĬodejock ActiveX components are standalone.

Platform: Visual Basic 6.0, Visual C#, Visual Basic.

Unicode ocx vb6