Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (2)

Resolved 64-bit Powerbuilder with oleobject

  1. Issue
0
Votes
Undo
  1. Haihong Yang
    Haihong Yang
  2. PowerBuilder
  3. Tuesday, 26 September 2017 23:40 PM UTC

Hi,

We are working on upgrade to Powerbuilder 2017. We tried to deploy 64-bit Powerbuilder application to Windows 10 System. We have some .Net Component communicate with PB using OLEobject call. All .Net component build as AnyCPU. But communication failed at ConnectToNewObject() call. But if we build 32-bit Powerbuilder application, it works fine. Can anybody give me some help?

 

Thanks      

  1. API
Making an object visible does now work outside of ...
PB2017 Bug #288
Responses (2)
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 11 October 2017 05:48 AM UTC
  2. PowerBuilder
  3. # 1

Hi Yang,

What's the OLEObject you used for the call. It should also be for 64-bit applications.
For example, the DLL or OCX the OLEObject used is for 32-bit applications, then there would be problems in calling them in 64-bit applications and you need to re-code them to for 64-bit applications.

Regards,
Ken

 

Comment
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Sunday, 1 October 2017 21:36 PM UTC
  2. PowerBuilder
  3. # 2

Are you creating 64 bit registry entries using the 64 bit version of REGASM for your 64 bit application?

There are two different locations in the registry for looking up the entries, one used by 32 bit applications (including the PB IDE) and one used for 64 bit applications.

Whenever you get an error message from something like ConnectToNewObject it would be useful if you would provide the error number.  That helps track down the issue.

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.