Hi, any example to work a window with header datawindow and detail datawindow in STD Framerowk?
- You are here:
-
Home
-
Q&A
-
Q&A
-
PowerBuilder
- Window with header datawindow and detail datawindow in STD Framerowk
-
Desarollo 07
- PowerBuilder
- Thursday, 2 May 2024 21:01 PM UTC
Hi Chris
I have this window and I want to double click on a record and show me the information from the detail tab using STD.
Comment
- Chris Pollach @Appeon
- Friday, 3 May 2024 17:03 PM UTC
Hi Desarollo;
Wow, that is a very old framework version & *not* compatible (or even migrate capable ) for use with PB 2022 R3!!!!
You should be using "STD_FC_Integrated_Framework_v2024.1.0.374_PB2022R3_B3289_2024-02-12.zip" or higher. release
=> https://sourceforge.net/projects/stdfndclass/files/FrameWork/Integrated
The "wn_extension" class and in fact all "extension" objects were *removed* in newer framework releases. The rational for that was: They took up PBL space, Slowed down the compiles; and added slower runtime performance (like the PFC does - way too much overhead). The idea here would be to allow the PB Developer to create the "extension" classes "only when need". So if you have code in that extension object class, please create your own "extension" PBL(s) in your App WorkSpace's Target as needed and then copy them to the newer PBL. If you do not have code in that extension class, then just ignore it an inherit your working Concrete classes from the Base level window ancestor (as appropriate) in the ".STD_FC_PB_Base.pbl;" library. HTH
Regards .. Chris
Wow, that is a very old framework version & *not* compatible (or even migrate capable ) for use with PB 2022 R3!!!!
You should be using "STD_FC_Integrated_Framework_v2024.1.0.374_PB2022R3_B3289_2024-02-12.zip" or higher. release
=> https://sourceforge.net/projects/stdfndclass/files/FrameWork/Integrated
The "wn_extension" class and in fact all "extension" objects were *removed* in newer framework releases. The rational for that was: They took up PBL space, Slowed down the compiles; and added slower runtime performance (like the PFC does - way too much overhead). The idea here would be to allow the PB Developer to create the "extension" classes "only when need". So if you have code in that extension object class, please create your own "extension" PBL(s) in your App WorkSpace's Target as needed and then copy them to the newer PBL. If you do not have code in that extension class, then just ignore it an inherit your working Concrete classes from the Base level window ancestor (as appropriate) in the ".STD_FC_PB_Base.pbl;" library. HTH
Regards .. Chris
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.
However, you are not allowed to reply to this question.
To do that operation, you would just use the standard PB events & methods. The Double clicked event to get the Row #, then the GetItemXxxxx() method to get the DB key. From there if the Detail Window was not open, then use an Open(Sheet)withParm() to display the detail. If then detail DWO is in a separate tab, then you just need a SetFocus() to have it displayed. I would them use the TriggerEvent () command to send that DW control the DB key in order to retrieve.
HTH
Regards... Chris