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

Resolved PB 2017 (using WizSource as SC)

  1. How-to
0
Votes
Undo
  1. Pieter Coene
    Pieter Coene
  2. PowerBuilder
  3. Thursday, 26 July 2018 13:55 PM UTC

Hi,

i have an issue with PB 2017 (R2) that we didn't have with PB 12.5

In PB 12.5, when you had an object that would not compile any more (ex. An object that inherits from another object, and in the ‘parent’ object, you change the return value to another datatype, so the ‘child’ object needs to be rebuild to ‘get’ the change), we did the following:

  1.  “Check out” the object -> normally you get an popup that the object has errors BUT the checkout was succesfully done
  2. Open the object with ‘edit source’ (because the ‘normal’ way is not possible) and correct the ‘Error’
  3. “Check In” the object
  4. Now you can open the object in the normal way (‘edit’)

But in PB 2017 R2, PB crashes at step 1…

Anyone having the same issue?

Greetz
Pieter

 

PowerBuilder & Git & PBDOM170.PBX
Distributed power builder aplication
Responses (5)
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 27 July 2018 14:29 PM UTC
  2. PowerBuilder
  3. # 1

I've had this happen to me in PBv12.1.

The only way I could resolve it was to compile the object in question over and over, commenting out various section within the object until it generated a clean compile. Once that was done, work for a clean FULL BUILD.

Ensure that the PBLs in your Library List are in the correct order and that you have no test code included.

Once you have a clean Full Build, then you can return to the problem object and examine it in more detail. Usually your changes will actually take effect without blwoing up the app at this point.


Olan

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 17:54 PM UTC
  2. PowerBuilder
  3. # 2

it doesn't crash for me, works the same as 12.5.  check out, get the 'could not compile' error.  then it finishes checking out and i can use source editor to fix the error.

using wizsource and 2017R2 Build 1769

Comment
Pieter Coene
  1. Pieter Coene
  2. Friday, 27 July 2018 06:34 AM UTC
We are using the same build 1769...
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 16:40 PM UTC
  2. PowerBuilder
  3. # 3

Bummer .. I hate those abends as you have no idea what module is even having the issue!   :-(

Have you tried before the checkout ...
    1) Optimizing all your PBL's?
    2) Doing a Full Build (I would recommend after step #1 for sure)?

 

Comment
Pieter Coene
  1. Pieter Coene
  2. Friday, 27 July 2018 06:58 AM UTC
I have not tested this fully, but the order in which you execute things may have an effect.



Order 1: do the change -> regenerate the object that needs to be rebuild -> check out -> works fine

Order 2: do the change -> full rebuild the application -> check out -> crash



  1. Helpful
There are no comments made yet.
Pieter Coene
Pieter Coene Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 15:09 PM UTC
  2. PowerBuilder
  3. # 4

Yep, the "hard" crash as you describe...

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 14:34 PM UTC
  2. PowerBuilder
  3. # 5

Hi Pieter;

  Does the IDE do a "hard" crash (aka just "go away" ) or do you get an error message before the IDE terminates?

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.