Importing 32bit OCX in Jade 7

[Speirs]

Hi,
I'm having trouble importing a 32bit activex into a Jade 7 environment.

The control registers OK, and the sample app runs no problem, but when you go to External Component Libraries and try import it, it doesn't show up - I think its only showing the 64bit controls registered on the machine.
I have started up a 32bit Jade client, connecting to an app server, but this also can not see the 32bit activex's registered.
Starting up a single user 32bit dev environment doesn't work with Jade 7, since it only supports 64 bit single user nodes.

Have tried registering the control using the standard regsvr32 and windows\syswow64\regsvr32. Both register it OK and the sample app runs fine in both cases, but neither option shows the control in the Jade import wizard.

Any ideas how to import this 32 bit control?
Thanks

[ghosttie]

I got around it by importing the dll into a JADE 6 db, exporting it and importing the scm into the JADE 7 system

[BeeJay]

Hi,
I'm having trouble importing a 32bit activex into a Jade 7 environment.

The control registers OK, and the sample app runs no problem, but when you go to External Component Libraries and try import it, it doesn't show up - I think its only showing the 64bit controls registered on the machine.
I have started up a 32bit Jade client, connecting to an app server, but this also can not see the 32bit activex's registered.
Starting up a single user 32bit dev environment doesn't work with Jade 7, since it only supports 64 bit single user nodes.

Have tried registering the control using the standard regsvr32 and windows\syswow64\regsvr32. Both register it OK and the sample app runs fine in both cases, but neither option shows the control in the Jade import wizard.

Any ideas how to import this 32 bit control?
Thanks

The other option to try would be to run a 32bit standard client connecting to the 64bit DbServer or a 32bit AppServer that you connect the thin client to, assuming the machine on which the AppServer is running has the 32bit ActiveX control registered on it. In other words, it's the machine hosting the node, not the machine hosting the thin client, which determines what ActiveX controls are going to be available to import and the bitness of the AppServer that will determine what ActiveX controls are available for import.

Hope that helps,
BeeJay.

[Speirs]

Excellent, thank you that was the trick I was after, it has picked it up and imported nicely.
Thanks.