Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi There,
We are currently using a QlikView 32bit OCX control in a Win Forms Application.
I have been asked to try the 64bit version.
Is there something different I should be doing with the 64bit OCX control?
Thanks
We currently deliver a 32 and a 64 bit version of our application.
Register the 32 bit. Use it to drag/drop onto Win Form. Delete the three wrapper dlls and manually create them
Unfortunately there is a bug in Visual Studio 2010 and it does not properly generate wrappers for ocx files. So these wrappers need to be created using the utility, AxImp.exe. These wrappers are used to replace wrappers in Visual Studio as described below.
Click Start, point to All Programs, point to Microsoft Visual Studio, point to Visual Studio Tools, and then click Visual Studio Command Prompt. This command prompt will use a PATH environment variable that makes AxImp.exe available as a command.
To create these wrappers
AxQlikOCXLib.dll
QlikOCXLib.dll
QlikView.dll
execute the following commands from the Visual Studio command prompt
cd C:\temp\QlikView\x86
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\AxImp" QlikOcx.ocx
cd C:\temp\QlikView\x64
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\AxImp" QlikOcx.ocx
Close the command prompt.
Add the new dlls to your references.
When you app fires up ... test for 32 or 64 bit mode and add the appropriate folder for 32 or 64 bit OCX to the path. Then when your app tries to use the OCX, Windows will use the path info to find the correct dll.
During the VS build process the 32 bit installed app seems to be sufficient.
The above requires you install/register the OCX before our app can be used.
There also is a StartRegFreeOperation feature on the OCX that
This makes distributing your app much easier.
We currently deliver a 32 and a 64 bit version of our application.
Register the 32 bit. Use it to drag/drop onto Win Form. Delete the three wrapper dlls and manually create them
Unfortunately there is a bug in Visual Studio 2010 and it does not properly generate wrappers for ocx files. So these wrappers need to be created using the utility, AxImp.exe. These wrappers are used to replace wrappers in Visual Studio as described below.
Click Start, point to All Programs, point to Microsoft Visual Studio, point to Visual Studio Tools, and then click Visual Studio Command Prompt. This command prompt will use a PATH environment variable that makes AxImp.exe available as a command.
To create these wrappers
AxQlikOCXLib.dll
QlikOCXLib.dll
QlikView.dll
execute the following commands from the Visual Studio command prompt
cd C:\temp\QlikView\x86
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\AxImp" QlikOcx.ocx
cd C:\temp\QlikView\x64
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\AxImp" QlikOcx.ocx
Close the command prompt.
Add the new dlls to your references.
When you app fires up ... test for 32 or 64 bit mode and add the appropriate folder for 32 or 64 bit OCX to the path. Then when your app tries to use the OCX, Windows will use the path info to find the correct dll.
During the VS build process the 32 bit installed app seems to be sufficient.
The above requires you install/register the OCX before our app can be used.
There also is a StartRegFreeOperation feature on the OCX that
This makes distributing your app much easier.