1. Sivaprakash BKR
  2. PowerBuilder
  3. Tuesday, 5 March 2024 00:05 AM UTC

We are facing few weird issues in PB 2022 R3 build 3289, which we never faced in PB 2022 R2.  Not sure whether others are facing this issue or not.

Issue 1:
We migrated one project from PB 2017 to 2017 R3 to 2019 R3 to PB 2022 R2 to PB 2022 R3.

At runtime, we assign a datawindow object to a datawindow control, in an event.  That event is called from open event and again after successful save.  The command is

dw_1.dataobject = 'dw_one'

This was working fine in PB 2022 R2 and earlier.  After migration to PB 2022 R3, the application got closed after successful save [ we ran from IDE]. We could not understand why the application closed.  The same thing happened when tried to run with debugger.  It was so tough to identify this issue.  After a couple of days, we recollected that a similar window is working fine.  The difference was the above dw assignment.  When we commented out the above line, this window worked fine. 

Now we have a condition to assign the dataobject, so that it didn't get reassigned again.

Issue 2:

The application is frozen, after successful save and after the execution of the last line which sets the focus to a column with the following command.

dw_1.SetColumn('column1')
dw_1.SetFocus()

There are no other command to be executed after the SetFocus command.  The cursor could be seen at the designated column and all data are saved. But the application goes into frozen state.  Nothing could be done except to kill the application.

Couldn't understand how to resolve the above issue.  This is NOT happening in every screen.  So far, we have migrated around 30 windows and we have faced this issue in 5 windows.  

To re-create this issue, we started creating a window with required datawindow and we see that that new one works fine without any issue.  Then we started building again the window ( and datwindows) that we need, and that works. 

So far, we have re-created 4 windows successfully and lately we found the same issue in another window.  Today we plan to re-create that window again from scratch.

 Would like to confirm that those 5 windows were working fine PB 2022 R2. 

Not sure, whether it's a PB bug or code bug.   

Happiness Always
BKR Sivaprakash

 

David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Tuesday, 5 March 2024 15:19 PM UTC
  2. PowerBuilder
  3. # 1

I've not see or experienced that issue in PB2022R3, my gut is telling me that it's a coding issue but don't really have any ideas of what you could look for. You could use the PB Trace to create a trace file and see what is actualy happening?

It just feels like you are in a loop somewhere.

Regards

David

Comment
  1. Sivaprakash BKR
  2. Wednesday, 6 March 2024 05:34 AM UTC
Thanks David, these issues do not happen in every window. So far what we found is that it happens only in migrated window / datawindows. If we redevelop either the window or datawindows or both, the problem vanishes.

Re-develop means create a new window, copy / paste all codes from earlier window.
  1. Helpful
  1. David Peace (Powersoft)
  2. Wednesday, 6 March 2024 09:21 AM UTC
Can you then perform a diff on the two source files to see what makes the difference.
  1. Helpful 1
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.