Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Unresolvable external on a olecontrol

  1. Issue
0
Votes
Undo
  1. Arcady Abramov
    Arcady Abramov
  2. PowerBuilder
  3. Tuesday, 1 March 2022 10:18 AM UTC

Hello, all

We have a serious issue.

There is a complicated user object, inherited from OLE control, which is used by multiple applications.

We set it up in a separate PBL and compiled it separately.

Library lists of the main desktop applications contain reference to the resulting PBD.

From the PB IDE everything works fine.

But once the application is compiled we get an "unresolvable external" error, even though the PBD is in the same directory as the exe.

Important to note that the above PBD contain datawindow classes and they are visible to the windows in both design and runtime.

We work with PB 2021 R3 (1506)

What can we do in order to share this complicated object which contains a lot of code in itself?

 

Thank you

Arcady

  1. .EXE
  2. PowerBuilder (Appeon)
Default Printer not Set Correctly (Citrix Environm...
Upgrading Cloud App Launcher CAL in non-AppData Lo...
Accepted Answer
Arcady Abramov
Arcady Abramov Accepted Answer Pending Moderation
  1. Wednesday, 2 March 2022 05:17 AM UTC
  2. PowerBuilder
  3. # Permalink

Thank you again for all your help

The problem was that in the project class the common pbd became unchecked. The file was there, but the exe did not see it.

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 2 March 2022 15:30 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Responses (5)
Arcady Abramov
Arcady Abramov Accepted Answer Pending Moderation
  1. Wednesday, 2 March 2022 04:09 AM UTC
  2. PowerBuilder
  3. # 1

Thank you for all your help

Answers:

1. If the PBL is added into the liblist instead of a PBD, then everything is working. However, we work with a WizSource source control, which requires all the PBLs projects to be in the same workspace, otherwise it creates copies of it and makes it impossible to work. This is why we need the PBDs.

2. The application is 64bit, not the 32bit. PB code.

3. It fails on the same machine as the IDE and in the same directory.

4. The separate PBD is compiled in the same PB version on the same machine.

 

Arcady

Comment
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 2 March 2022 03:41 AM UTC
  2. PowerBuilder
  3. # 2

Hi Arcady,

Is this separate PBD file compiled in PB of the same version?

I suggest you compile the Main Desktop Applications together with the separate PBL file so that all the new created PBD contains the separate PBD file. Then run and see if it works.

 

Regards,

Ken

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 2 March 2022 01:24 AM UTC
  2. PowerBuilder
  3. # 3

Hi,

- Does it fail with the EXE on the same machine as where it works from the IDE or is it a different machine?

- Is it a Visual ActiveX control that might need an installer?

- Does it work if you just add the PBL to your executable instead of the PBD?

regards

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 1 March 2022 20:33 PM UTC
  2. PowerBuilder
  3. # 4

Hi Arcady;

  If it works when run from the from the IDE - hen it should work just as well from an EXE as long as the App was compiled into 32bit P-Code. The only reason (this I can think of) for it not working is the App performing a SetLibraryList command and accidentally taking out the PBD that contains the User Object & DWO's.

Regards ... Chris

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.