cancel
Showing results for 
Search instead for 
Did you mean: 

PB 12.6 Classic .ConnectToNewObject("clsid:xxx") return -3

Former Member
0 Kudos

Hi All


PB 12.6 Classic


Run 32 bit app (exe) in 64 bit OS try ConnectToNewObject("clsid:xxx") to 32 bit activeX return ok.

Run 64 bit app (exe) in 64 bit OS try ConnectToNewObject("clsid:xxx") to 32 bit activeX return -3 (object could not be created).

.


dll is register on SysWOW64


What's is wrong?



Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Rafał ;

  FYI: You must use a 64bit OCX/OLE object when running & connecting from a PB application which is also generated as a 64bit EXE.   

HTH

Regards ... Chris

Former Member
0 Kudos
Former Member
0 Kudos

Thank you .. Very interesting for sure!

Did this work for you?

FWIW: My issues with this approach - being with the Canadian Federal Government - would be to roll this out into production where the PC's are basically locked down from making these type of registry changes. This would have to be pushed out through SMS maintenance by the production support teams. A nightmare to get them to do this without "jumping through hoops" plus, a few dozen key signatures.