Appeon Comunidad

1. No "Invalid DW row/column specified" error for row 0

   Hello,

   I started noticing quite some time ago (maybe in PB 12.5, maybe earlier) that PB stopped throwing an error when GetItemX datawindow method is called with row 0. Now, when it happened again in PB2019 R3, I decided to isolate the issue. I created a simple DW with an external data source, one string column "s", and data "ABC". I placed a DW control on a window, and wrote the following datawindow control clicked event script:

   messageBox( 'Data in clicked', getItemString( 0, 's'))
   

   When I run the window and click the DW, I get a nice message box:

   

   If I misspell the column name, however:

   messageBox( 'Data in clicked', getItemString( 1, 'sss'))
   

   I still get the good old Invalid DW row/column specified error:

   

   Of course, if both row and column are correct, I get "ABC":

   messageBox( 'Data in clicked', getItemString( 1, 's'))
   

   

   Does anybody know why this is happening?

   Best regards,
   Konstantin

2. PB 2019 R3 to 2022 R3 migration - Platform compliance

   Hi,

    

   As mentioned in the PowerBuilder 2022 R3, IDE will support windows 11 and Run time will support both windows server 2022 and windows 11.

    

   Will PowerBuilder 2019 R3 Runtime will also support windows 11 and windows server 2022, currently we are using windows server 2016 and windows 10.

    

   Kindly reply on this to proceed further with migration.

    

   Thanks,

   Tharani S

3. Predefined error_message pfc_dwdberror

   Hi,

   After installed PB Runtime 22.2.0.3356, i have change the PB application.xml file to point "C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.2.0.3356" then launch our application.exe then getting below error,

   

4. Strange behavior in PB 2022 R2 Build 2819 - decimal places in DW edit columns set to 0

   Hi,

   since 2 months we are confronted with an issue in our app wich ends in setting the decimal places of a floating number to "0". 

   This happens immediatley after entering an decimal number and leaving the column. The digits after the floating point are set to "0". The number of the digits corresponds to the defined display format. After that an update() saves the numbers with ".00" to the database. This is a serious problem for us. 

   We can't reproduce the problem at any time.

   The columns where the problem occurs have columntype "number" and are defined with a display format (eg. #,##0.00). In some cases an edit format ist defined (eg 0.00). 

   Currently we use PB 2022 R2 Build 2819.

   Does anyone knows how to solve this issue? 

   We found a posting to an similar problem (https://community.appeon.com/index.php/qna/q-a/computed-expression-decimal-point-issue). But we allready use a newer build.

   Thanx! 

5. PB 2019 R3 to 2022 R3 migration - Window Resize

   Hi,

   
   I migrated to PB 2022 MR 3356 Build, as mentioned in the link https://www.appeon.com/standardsupport/search/view?id=11486.
   
   If i have done the code change related to window height in open event, to display the controls properly.

    

   But in future will it there any update build will be provided for this problem.
   
   If so then do, we need to rollback our code again?