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

Resolved Compiled files from IDE differ from compiled files from Autocompiler

  1. Issue
0
Votes
Undo
  1. Gene Kanten
    Gene Kanten
  2. PowerBuilder
  3. Thursday, 28 January 2021 19:01 PM UTC

We are using PowerBuilder 2019 R2.  (19.1.0.2353)

When we run our application, that was generated using the autocompiler (pbc190.exe) we are getting an error:

When we build the application using the IDE and run it there are no errors.

There are some file size differences between the two for some of the .pbd files that get created.

There seems to be an issue with the autocompiler.

I've checked that the versions match.

Has anyone else run into this issue?

Anything else I can check?

 

 

 

  1. AutoCompiler
  2. PowerBuilder Compiler
WebBrowser Feature missing.
Runtime files
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 28 January 2021 22:47 PM UTC
  2. PowerBuilder
  3. # 1

Why would you get a runtime error in the compiler? Bizarre.

Comment
Gene Kanten
  1. Gene Kanten
  2. Friday, 29 January 2021 01:12 AM UTC
Hi Roland,



The runtime error is not in the compiler, it is in the executable created by the compiler.

The compiler runs without any errors.



If i create the executable with the IDE I don't get the runtime error.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Friday, 29 January 2021 13:55 PM UTC
Add some debug messages or logging so that you know:

What is the datawindow object

How many rows in the datawindow/datastore

What row was passed to the GetItemXXX call

What column was passed to the GetItemXXX call



Maybe the datawindow object didn't get included in the PBD which leads to zero rows retrieved.
  1. Helpful
There are no comments made yet.
Gene Kanten
Gene Kanten Accepted Answer Pending Moderation
  1. Thursday, 28 January 2021 19:28 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

The command line compiles all the targets in the workspace (there are 4 targets). It's pretty simple and is using the defaults: 

pbc190.exe /d csland.pbw

I do have three different versions of PB on my PC (12.5.2, 2017 R3 and 2019 R2), which is where I have been testing. I don't know if that might cause an issue. We are using Git for SCC. We aren't using any resource files.

On our build server we only have the PB 2019 R2 autocompiler. On the build server we specify more command line arguments but the result is the same, it also generates the error.

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 28 January 2021 19:42 PM UTC
Hi Gene;

This sounds like a "reproducible" issue. If so, please open a Support Ticket for this problem.

http://www.appeon.com/standardsupport

Regards ... Chris
  1. Helpful
Gene Kanten
  1. Gene Kanten
  2. Thursday, 28 January 2021 19:53 PM UTC
OK. Thanks Chris.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 28 January 2021 19:09 PM UTC
  2. PowerBuilder
  3. # 3

Hi Gene;

  In the PB external compiler ... check if the command line entries package your DWO's properly via a PSR file assignment or via marking the PBL where the DWO's reside either a PBD or DLL.

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.