Hi All,

Good news that PowerBuilder 2021 GA (build 1288) is available for download. The
issue you reported has been fixed in this release. Please download and install
it to verify the issue you reported and let us know if any problems. 
You can get the installer from our Downloads portal at
https://account.appeon.com/download (login required).
 
In this version, we have enhanced the PrintGetPrinter function to gain the default printer in real-time. 
Previously, the printer name the PrintGetPrinter function gains is the default printer when the app is launched. And this printer name now won’t be changed regardless of the modification of the Windows default printer settings, but you can use the PrintSetPrinter() commands to set the new default printer.
 
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:
You should add a pb.ini file in the directory where the EXE resides, this pb.ini file contains the below content:
[Application]
Citrix=1  
 
We welcome all feedback from you!


Regards,

Not to pile on, but...

I'm having the same problem.  I've got a very large MDI application, with dozens and dozens of windows. This code has been running for 20+ years, through all the migrations. All of the sudden, my print functions don't work properly.  

Print Setup isn't changing the Windows default printer

Print is ignoring the chosen printer and printing to the (old) default

Print Immediate IS remember what was set in Print Setup.

Very frustrating! This is a commercial application I resell to other corporations, and I don't feel like I can release the new version with these printing bugs. And they are BUGS...

Right now I feel like upgrading to Appeon's version of PB was a mistake...

~~~Tracy

 Hi Kevin,

After having a few meetings with Selvam, we found out a solution and provided a new PBSHR190.dll file for him and he confirmed that it works (Ticket 5874).

Attached you can find the PBSHR190.dll file. If you confirm that your issue is the same as his, you can:

1. Try to upgrade your PB to PB 2019 R2 2353.
2. Backup the original PBSHR190.dll file.
3. Replace the old one in the runtime folder with the attached one and see if it resolves your issue.

Regards,

Hello,

We have the same issue.  Using PB2019 R2 build 2328 connected through Citrix.  We are unable to see the default printers.  We have no issue when using PB12.5 version.

The only option from the "Print Setup" window is..
Sybase DataWindow PS on FILE:

Is there any patch or fix for this issue?

We use Citrix to host a lot of our big Customers.  This will impact and hurt our business really bad.

Any suggestions?

Thanks,

Kevin

Hi Ameen

Finally we have rolled back to PB2017 and no printing issues.
As you have mentioned, I have created two sample test applications in PB 2017 and PB 2019.

click on File- Print Setup 
It will point to correct default printer in Citrix environment for PB 2017 application.
Click on Call Api button it will show correct default printer when PrintGetPrinter as well as GetDefaultPrinterW called.

SetDefaultPrinterW does work fine.

Migrated that into PB2019
It will not point to correct default printer when we do print setup.
Always points to Microsoft XPS Document Writer when PrintGetPrinter called.

GetDefaultPrinterW  works fine but SetDefaultPrinterW does not work.

It does look like a regression bug.
Please let me know.

Thanks
Selvam

Hi Chris

I have tried your workaround of writing the default printer in ini file. 

Printgetprinters works fine but printsetprinter fails.

Support team are saying PB2019 R2 cannot support windows server 2008, that could be the issue.

Apparently PB2019 supports windows server 2008 .

My question is there anyway I can go back from PB2019 R2 to Pb2019?

This way I can solve the issue quickly.

Our application is pure client server application, no power server or web involved.

Please let me know.

Thanks

Selvam

Hi Selvam;

  I was pretty sure that MR2353 would not be the answer as it contained no printer fixes. Either my suggestion in ticket #5864 or Olan's would be the workaround(s) for now AFAIK.

  Lets see what the main Support / Engineering says on the open ticket.

Regards ... Chris

I have the exact same setup.

My solution was as follows:
1. On the main window, there is a field that shows the current printer

2. On the main window, there is a button that pops up a response window that allows the user to select which printer they want.

3. If the user selects a different printer, the Windows Registry is updated to the newly selected printer, the "Current Printer" field is updated, and PrintSetPrinter(<new_printer>) is called for the app/


Olan

Selvam;

  Thank you for opening up ticket # 5874. I have made a few suggestions in my reply and also forwarded this over to the main Support / Engineering Team. I checked in the MR #2353 and there are no Citrix/Printer fixes listed there but, it might be worth trying that MR if you have some time to test. In the mean-time, lets see what feedback we get from the main support team.

Regards ... Chris