Release Bulletin for PowerBuilder
Build 1878 (GA)

(Fixed in MR 1892) (PostgreSQL + ODBC) In the OS where a comma is used instead of a decimal point in decimal numbers, the comma will be missing, which could result in significant increase of the number.

(Fixed in MR 1892) The window size on the PowerBuilder IDE design interface is inconsistent with the size when demo is running. The actual window interface is wider and longer.

(Fixed in MR 1892) In 64-bit OS, if you input any character in the EditMask control, and then press the tab key or click the first input box in EditMask with dates, the number or character cannot be input.

(Fixed in MR 1892) When directly running the demo, only a blank window opens, but no messagebox pops up. The icon property is set in the open event, so that the show event cannot be triggered.

(Fixed in MR 1892) The JSON file in Export build files only contains the name and path of the INI file, but not the parameter of update strategy. Or, PBAutoBuild220.exe handles INI file update processing without reading the parameter of update strategy.

(Fixed in MR 1892) The change of the region settings will cause the changes in date format so that the program cannot be read correctly to the end, which makes the array storing the date out of bounds, causing IDE crash.

(Fixed in MR 1892) Every time you set the window height from runtime, some PBU is added. Please refer to Window size differences for more details.

If the URL of PowerBuilder/InfoMaker Installer is launched within the MS Office (such as Outlook, Word, Excel, etc.), Windows SmartScreen will display a warning before downloading the installer via the Web browser: "XXX could harm your device. Do you want to keep it anyway?" XXX could be any executable file that SmartScreen considers as not well-known or not many downloads. This is normal protection behavior of Windows SmartScreen. You can click Keep to continue; or open another Web browser and then launch the URL of PowerBuilder/InfoMaker Installer from there (to avoid the warning).

When inserting an Excel file to the RichTextEdit control using the InsertDocument function, only the first sheet can be inserted. You will be able to select which sheet to insert in the next release.

If the PBL contains an incompatible version of PBDOM objects, PowerBuilder IDE will crash when opening the PBDOM object or deploying the PowerServer project. To resolve this issue, you will need to import the latest pbdom.pbx or add the pbdom220.pbd file to the PBL list.

64-bit debugging has the following known issues:

In PowerBuilder GA 1878, the CEF version of Web browser is upgraded to chromium-102.0.5055.63. However, this version of Chrome handles personal configuration information differently. Even if you accept the terms of use, the next time you open the browser you are asked to accept it again. This problem will persist until PowerBuilder figures out how to change this default behavior of Chrome in a reasonable way.

When using PBAutoBuild to deploy an application, it takes longer than when using PowerBuilder IDE. This is an expected behavior. PBAutoBuild can be used freely outside PowerBuilder IDE. It has different compilation logic and uses different compilation methods. Moreover, it has more internal detections and error correction functions than PowerBuilder IDE, which cause differences in performance. For example, using OrcaScript to import objects to PBL fails while using PBAutoBuild Merge can succeed. If the PowerBuilder application is small, for example, the Sales demo, then the performance of PBAutoBuild is close to that of PowerBuilder IDE, but if it is a large and complex application, the performance of PBAutoBuild is much slower than PowerBuilder IDE, possibly 50% or more.

(PowerServer) Database synonym does not support 1) cross-database references and 2) the DefaultValue property of columns.

PowerBuilder IDE 2022 GA can only work with PowerBuilder Runtime 2022 GA and official releases (such as the coming MRs); and does not work with PowerBuilder Runtime 2022 Beta or temporary releases (such as one-off builds and private builds).

If the installable cloud app name contains multiple byte characters, the ProfileString function will fail to parse the app path that contains multi-byte characters. As a workaround, you can change the regional format of the client OS to the language of the multiple byte characters.

If the installable cloud app is installed to a path which contains multiple byte characters, the loading of the 64-bit runtime files will fail.

If the PBR file has references to file name that contains multiple byte characters, the characters will become unrecognizable during compilation and the corresponding file will not be deployed with the app executable file, thus the app cannot find the file. As a workaround, do not place file name that contains multiple byte characters in the PBR file; or add the file as External Files and then deploy the PowerClient/PowerServer project.

If you change the Platform settings (32-bit or 64-bit) of the PowerServer project and then click "Deploy PowerServer Project", the change will be effective to only the runtime files, but not the app executable file, thus the app executable file will fail to load the runtime files. To resolve this issue, you will need to click "Build & Deploy PowerServer Project" (instead of "Deploy PowerServer Project") to make the change effective to both the executable file and the runtime files.

When the PBL list has changed, if you build & deploy the project without re-opening the PowerServer project painter, the library list in the project painter > Client App page > Advanced tab will fail to update and deploy correctly. To resolve this issue, close and open the PowerServer project painter and then build & deploy the project again.

If you specify the command line arguments for the installable cloud app, the argument string cannot contain over 512 characters, otherwise the application will crash.

If you add a PBD file to the library list of an application target from a directory that is different from where the target is stored, the PowerServer/PowerClient projects created in the target would fail to open. The reason is that the PBD file is added to the library list via the function GetFileOpenName, and the function will change the current working directory. The solution is to reset the working directory to the directory of the target.

(Oracle database) The multi-byte characters will display as error code ("?") when the DataWindow is dynamically created.

If you select the "Skip" option for "If Cloud App Launcher or runtime files (with the same major version) already exist" and then select to deploy a public version, the public version cannot be deployed successfully if a standard version already exists in the Web server. In this case, you can switch "Skip" to "Overwrite" and then deploy the public version again; or you can upload (or zip and then upload) the public version using the Upload Cloud App Launcher and Runtime tool.

If you install the public version of cloud app launcher in a silent mode with non-administrator rights, you will not be prompted for insufficient rights and the installation will fail directly.

The functions included in the label functions cannot use local variables to receive values from "SELECT INTO". For example, if functionA() included in the label functions contains the following scripts, then functionA() will not work as expected.

String ls_Name, ls_Desc
//Local Variables
SELECT Name, Ddesc  INTO :ls_Name, :ls_Desc  FROM Dept  WHERE ID = '100';

As a workaround, you can change the local variable to global variable in functionA(). For example,

//Global Variables
SELECT Name, Ddesc  INTO :gs_Name, :gs_Desc  FROM Dept  WHERE ID = '100';

The starting and ending of the PowerServer debugging will be slower than that of the normal application debugging.

If you open the PowerServer/PowerClient project configuration window during a debugging process, you cannot return to the debugging window, unless you exit and then restart debugging.