Using COM Components Between Different Platforms (32-/64-bit)

Valid for: enaio® version 10.0

To allow COM components (DLL) to be used between different platforms (32-bit Windows DLL and 64-bit Windows EXE), the Windows Registry must be modified. For this, the COM components must already be registered. As part of the customization, Windows automatically creates a runtime environment for the COM component and communicates with COM-DLL and the calling application across processes. This approach is not normally possible with COM components such as OCX and ActiveX, but these are also not usually used for scripting. Therefore, please test the functionality of the corresponding COM component beyond the platform boundary.

By way of example, we will now show you how to use the OXVBBAS library (Dim oxbas : Set oxbas = createObject("Oxvbbas.functions")) in 64-bit server scripts, as required for the ad-hoc workflow.

Other examples concern the connection of the enaio® client (ANSI/32-bit) to an installed 64-bit Microsoft Office and of the enaio® client (Unicode/64-bit) to an installed 32-bit Microsoft Office. The latter examples are connected via the corresponding redemption libraries from the client installation directory for creating e-mails.

For project-specific components, these registry adjustments must be made according to the following schema.