• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Open(window, parent) Function in Powerbuilder 12.6 (After migration from 12.1)

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

Resolved Open(window, parent) Function in Powerbuilder 12.6 (After migration from 12.1)

  1. Issue
0
Votes
Undo
  1. Ken Rigalado
    Ken Rigalado
  2. PowerBuilder
  3. Wednesday, 13 January 2021 03:34 AM UTC

Hi, we have an application developed in Powerbuilder 12.1 which we are migrating to Powerbuilder 12.6 (4138), there are some challenges encountered during our testing (which we anticipated) but this one is a showstopper for us as we are stuck to identify what the issue is.

This is only an issue in 12.6 and is working fine in 12.1.

The problem is the line below in an event on window w_main:

uo_1 is a variable of a window type for a window named wasset100.

Ideally what's happening is that the Message 1 will show, open the window wasset100 then return the process back to w_main to execute a few more lines (or show Message 2). This is also how it goes in 12.1.

In 12.6 the process failed to return in w_main so the Message 2 is not showing after opening the window wasset100 . I have a few more messagebox in the Open event of the wasset100  window and also able to debug so I can confirm that the system is able to open the wasset100 window. Only problem is that it is not returning to w_main to execute  the lines after the open function.

Hope you can help.

Thanks!

 

  1. PowerBuilder
  2. PowerBuilder (Appeon)
Using PowerBuilder Autocompiler in Azure pipeline?
64 bit vs 32 bit
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 January 2021 16:34 PM UTC
  2. PowerBuilder
  3. # 1

Hi Ken;

  FWIW: PB 12.6 was a poor release for SAP as it had "tons" of MR's and EBF's for a few years after its release to try and stabilize it and fix various regression bugs. Plus as John pointed out, it's a deprecated release now and no longer has any support since 2017.

  My suggestion is to think about downloading an Appeon PB release and then look at migrating your PB 12.1 Apps to one of these supported releases (PB2017 R3 or PB2019 R2). Just my $0.02.

Regards ... Chris

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 13 January 2021 16:36 PM UTC
right, and for your comfort: Appeon 2017 and 2019 were build parting from that shaky 12.6 :)
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 13 January 2021 16:38 PM UTC
(not saying the advice is not a good one).
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 13 January 2021 12:03 PM UTC
  2. PowerBuilder
  3. # 2

try to move all the code of the open event to an event that is called with POST from the open event.

see what happens. It's never been a very good idea to call MessageBox() from an open event.

regards.

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 13 January 2021 05:18 AM UTC
  2. PowerBuilder
  3. # 3

Hi, Ken -

Some ideas I would try if I were in your shoes:

1. Temporarily open a different window instead of wasset100 to see if execution returns to the SelectionChanged event script. Maybe something in wasset100 is now inadvertently causing the issue in 12.6.

2. When debugging the Open event in wasset100, does the execution call stack show execution came from the SelectionChanged event of tab_1 in w_main? What about when debugging same code in v12.1? Look for any differences.

3. Temporarily open the wasset100 window using the implicit global variable named wasset100 instead of the reference variable uo_1: Open(wasset100,Parent)

4. Temporarily try OpenWithParm and send a dummy parameter/object to wasset100 to try using a different "open" PowerScript command.

You realize, of course, that PB v12.6 is functionally obsolete and is no longer supported. Have you considered upgrading to Appeon PB? [no, I do not work for Appeon ;-) ]

HTH

Regards, John

Comment
Ken Rigalado
  1. Ken Rigalado
  2. Wednesday, 13 January 2021 06:09 AM UTC
Hi John, thanks for the reply I already tried your suggestion on 1, 3 and 4 but to no avail. How do I check #2? Where can I see this?
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 13 January 2021 12:09 PM UTC
About John's #2:

While debugging, you can inspect the 'stack' on the right lower part of the IDE, where the 'breakpoints', 'watches' and 'call stack' are shown as tab pages.
  1. Helpful
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.