-
Ravi Teja K
- PowerBuilder
- Wednesday, 8 July 2026 01:02 PM UTC
Hi Appeon Team,
We are facing a display issue after migrating our application from PowerBuilder 2017 (v10.6) to PowerBuilder 2022 R3.
Customer environment: Citrix (Windows Server) Local environment: Windows 11 with dual monitors SQL Server backend (not related to this issue)
Issue Description: The Product Search response windows (w_product_pharm_s and w_product_pbs_s) do not display correctly when the application is opened on the secondary monitor. The customer first reported this issue in their Citrix environment. We have reproduced the same behavior locally using a dual-monitor setup.
Symptoms :
The Product Search window does not fit entirely within the visible client area.
The lower part of the window is hidden.
The OK, Cancel, and Help buttons remain hidden until the window is manually moved.
The window appears larger than the visible area.
The same window displays correctly on the primary monitor.
This issue does not happen in the PowerBuilder 2017 version of the application.
Customer Information The customer confirmed the following:
The issue occurs for all users.
It happens every time on the secondary monitor.
The issue has only been seen with the Product Search window.
It occurs in several modules, including: - Dispensing - Distribution - Suggested Use Order Worksheet - Stocktake - Borrow/Lend - Loan Repayment - Manufacture - Product Site - Both monitors have the same resolution and display scaling.
The issue still appears even if the application is initially opened on the primary monitor and then moved to the secondary monitor. (Windows Display Settings and Citrix Workspace details are attached.)
Investigation Performed We have done thorough investigation within our application.
Window Investigation We reviewed the following windows: - w_product_pharm_s - w_product_pbs_s - w_search - w_response - pfc_w_response This included their Open, pfc_PreOpen, pfc_PostOpen, and resize-related logic. Previous PB2022 Migration Changes During our PB2022 migration, we encountered similar display issues in several other windows. Increasing the window height fixed those problems. To see if the Product Search window might be affected similarly, we tried adjusting its height. Result: No change. The issue remained. Window Positioning We looked into the common response window positioning logic, including: - WorkspaceX() - WorkspaceY() - MDI_1 calculations - THIS.Move() We also tested by removing the active sheet offset calculations used for positioning the response window. Result: No change. Resize Framework We examined the PFC resize framework (Of_SetResize / pfc_n_cst_dwsrv_resize).
We confirmed that: - The resize service stores the original window size. It resizes registered controls during Resize events. It does not change the parent window size or initial position.
Runtime Debugging Runtime debugging confirmed that: - The Open event executes without issues. The Move event executes successfully. Resize events execute without issues. No runtime exceptions occur. Window positioning calculations seem valid. The issue can be consistently reproduced on the secondary monitor. Current Findings From our investigation, we found: - The issue occurs only after migrating to PowerBuilder 2022 R3. - The same application works correctly in PowerBuilder 2017. The problem happens only on the secondary monitor. - We have reproduced the issue both locally and in the customer's Citrix environment. Previous window height adjustments do not fix the issue. The PFC resize framework is not responsible for the behavior. - The application logic for opening and positioning the response window seems to work as expected. At this point, the behavior seems related to how PowerBuilder 2022 R3 handles rendering or positioning MDI response windows on a secondary monitor, rather than an issue with the application logic itself.
Questions Could you please advise: -
1. Is this a known issue or limitation in PowerBuilder 2022 R3?
2. Are there any runtime patches, EBFs, or workarounds for this behavior?
3. Are there recommended changes to MDI response window positioning after migrating to PB2022?
4. Are there known issues related to dual-monitor or Citrix environments that could cause response windows to open partly outside the visible client area?
5. Are there PowerBuilder runtime settings or manifest changes to consider for PB2022 R3 applications running in multi-monitor environments?
I am attaching customer issues as attachments also their resolution details. Can you kindly review and suggest.
Thanks & Regards,
Ravi Teja K
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.