1. Balasubramanian Natarajan
  2. PowerBuilder
  3. Wednesday, 29 June 2022 06:36 AM UTC

Hello Everyone,

We are launching an application from Citrix Server from our local workstation after the application is opened user clicks the File --> PrintSetup menu, in the Print Setup window the default printer shows as the citric server default printer but it should show the local workstation printer.

Below is the 1 line code in PrintSetup menu

PrintSetup()

Expected: The default printer for the application should be the default printer on the workstation.

Actual: The default printer is the default printer on the Citrix server and needs to be manually changed

PowerBuilder Version: 2017 R3 Build 1880

Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 30 June 2022 07:23 AM UTC
  2. PowerBuilder
  3. # 1

Hi Balasubramanian,

 

It seems that it is a known issue. Please refer to the following link for the detail for working it around.

https://community.appeon.com/index.php/qna/q-a/pb2019-r2-build-2328-default-printer-setting-issue

I suggest that you try to upgrade your PB application to PB 2021 Build 1509. In PowerBuilder 2021, if you are using Citrix, you can get the Windows default printer in real-time dynamically once the following configuration is set.

Adding a pb.ini file in the directory where the EXE resides, this pb.ini file contains the below content:

[Application]

Citrix=1 

 

Additionally, if you still have this issue after upgrading PB, kindly please report this issue to our ticket system: https://www.appeon.com/standardsupport/newbug so that it can be properly received and tracked. Please also provide a sample PB test case (with PBT / PBL) when you submit it to the ticket system.

 

Regards,

Comment
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 29 June 2022 13:19 PM UTC
  2. PowerBuilder
  3. # 2

A quick search of the Bug Reports showed this:

   https://www.appeon.com/standardsupport/search/view?id=6261

From the content in this ticket, it sounds like upgrading to a newer maintenance release (Build 2703) of PB 2017 R3 might address the issue you are experiencing.

Regards, John

Comment
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.