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

Resolved How to debug this issue?

  1. How-to
0
Votes
Undo
  1. Sivaprakash BKR
    Sivaprakash BKR
  2. PowerBuilder
  3. Monday, 4 March 2024 11:38 AM UTC

Hello,

Using PB 2022 R3, build 3289

The below window has been migrated from PB 2022 R2.  It has one datawindow at top, with details, of Date, Location and Retrieve button.  Another datawindow at bottom, to enter, Item details with quantity [ quantity fields and other fields are not shown here ].

No Tab order for the 'Retrieve' button.   It works fine.  

When we assign a tab order for the button, on clicking of the button, the application closes.  [ We run the window from the IDE].  If we remove the taborder for the button, the window works fine.

How to debug this issue?

Happiness Always
BKR Sivaprakash

 

  1. PowerBuilder (Appeon)
To open a window as reponse as well as main window
Font size in Database Result tab
Responses (5)
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Tuesday, 5 March 2024 15:18 PM UTC
  2. PowerBuilder
  3. # 1

If it works in R2 and not R3 I'd report it as a bug!

Comment
There are no comments made yet.
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Monday, 4 March 2024 11:45 AM UTC
  2. PowerBuilder
  3. # 2

It sounds like a PB bug.

You could try the pbdebug option to create a log of executed code. Maybe you can find out what happens.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 5 March 2024 16:46 PM UTC
FWIW: the other scenario that I have used before is to comment out all the DW Control event scripts. Then add them back one by one until the error resurfaces. then you will know which event's code is causing the issue. Food for thought. ;-)
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 4 March 2024 14:20 PM UTC
  2. PowerBuilder
  3. # 3

If you are using a Button DWObject (a button object within the DataWindow), then perhaps instead try using a Command Button control placed into the Window as an alternative.

Comment
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Monday, 4 March 2024 15:42 PM UTC
  2. PowerBuilder
  3. # 4

What events are you using to capture the button being clicked and what code?

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Tuesday, 5 March 2024 00:13 AM UTC
Thanks David,

Only one event, buttonclicked event. It calls another event(s), based on a condition.



If dwo.name = 'b_retrieve' Then

If conditionone = onevalue Then

Event ue_retrieveprocess_retrieve_one()

ElseIf conditionone = anothervalue Then

Event ue_retrieveprocess_retrieve_another()

End If

End If



Event ue_retrieveprocess_retrieve_one() and ue_retrieveprocess_retrieve_another()

retrieves data from different tables.

  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Tuesday, 5 March 2024 09:42 AM UTC
I have just created a small test and cannot reproduce your problem. I wonder if the issue is related to the code in the other events?

Have you tried setting a breakpoint on the first IF statement to see what happens?
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 4 March 2024 16:26 PM UTC
  2. PowerBuilder
  3. # 5

There's bugs with dw buttons having taborders reported quite some time ago. Doesn't seem to be a priority.

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Tuesday, 5 March 2024 00:14 AM UTC
It was working in PB 2022 R2, PB 2019 R3 and down. Only in PB 2022 R3 we face this issue.
  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.