• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Migrating from Pocketbuilder 2.5.2 to Powerbuilder 19 r3

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

Resolved Migrating from Pocketbuilder 2.5.2 to Powerbuilder 19 r3

  1. How-to
0
Votes
Undo
  1. Alwin Wolfgang
    Alwin Wolfgang
  2. PowerBuilder
  3. Thursday, 27 May 2021 09:43 AM UTC

Hello,

We are in the process of migrating a pocketbuilder application to powerbuilder.

what did we do?

1. we migrated from Pocketbuilder 2.5.2 to Powerbuilder 10.5 

    After the migration we fixed the errors and warnings. The application ran oke and we could change (data)windows

2. we than migrated from Powerbuilder 10.5 to Powerbuilder 17 r3

    After the migration we fixed the errors and warnings. The application ran oke and we could change (data)windows

3. we than migrated from Powerbuilder 17 r3 to Powerbuilder 19 r3

no errors to fix, the application runs but.. 

The following happens when we try to run a lot of the windows or try to change them in Powerbuilder: Powerbuilder closes without warnings or errors. Not all windows react this way, but a good deal of them.

question: as we have no leads as to what is going wrong, we can not fix the problems. 

Who has an idea for a solution? Who has a suggestion? Can we create a LOG file to view the errors?

Help would be appreciated!

Cheers, Alwin 

 

ASTM Protocol data reading
Re: Windows Server 2008R2 and PB 2019R3 Theme
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 27 May 2021 17:24 PM UTC
  2. PowerBuilder
  3. # 1

A common cause of unexplained aborts is a Windows API call with uninitialized string arguments.

If a string argument is by ref, you must use the Space function first to allocate enough memory to hold the expected output of the API function.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 May 2021 16:07 PM UTC
  2. PowerBuilder
  3. # 2

Hi Alwin;

  If Roland's great suggestion fails to correct the issue ....

  FWIW: I had a separate PocketBuilder framework, EAServer Framework, Web Framework and native PB Framework and then merged all of them into one on June, 2013. You can see the related presentation here (check out slide #5) - http://sourceforge.net/projects/stdfndclass/files/Presentations/PBTV/Integrated%20Framework

  If you download the current Framework's Demo App and search for PocketBuilder (PK) - you will still see comments around this old product's features that were converted to be native PB and PowerServer "mobile" compliant. HTH

  Also, check out the logging feature in my framework. If you adopt that feature into your PB App, it could reveal a lot about what the App was doing just before it crashes. Of course, there is still no substitute for the PB IDE's "debugger" in "step" mode.  ;-)

Regards ... Chris

 

 

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 27 May 2021 12:34 PM UTC
  2. PowerBuilder
  3. # 3

I would start by running a Full Build on the target and then an Optimize on every library.

 

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.