In PB 2022 compile as 32-bit app see if the issue persists so we can narrow down if some difference between PB 2019 and 2022 or if it is because you switched from 32-bit to 64-bit project?

Also, are you using exact same version and build of pdftk as before?  Or when you upgraded PB you also upgraded to newer version of pdftk?

Hi Satish;

  I use the PDFTK product with PB 2022. The PDFTK is run externally to your PB App - so it's unlikely to be the issue (logically speaking).

  If you are now using the NativePDF feature though, there are open tickets around the font & overlapping field issue that Engineering are looking at.

  However if you are using the NativePDF feature please make that A) you have the correct NativePDF runtime DLLs in production and B) try changing the Apps "Default" printer in production to see if that rectifies your PDF generation problems.  HTH

Regards ..  Chris 

I am having a strange problem after the same upgrade but maybe it has to do with me needing to rebuild in 32bit. I will try that but just to explain what I'm experiencing, I can generate PDF's from the development environment (when I run the app) without a problem but users cannot. I tried to copy a version of the application to my local drive and I also can't generate PDF's when i run the app locally - outside of the development environment. If I removed the pbvm.dll, i can generate a PDF without a problem but then other users will get an error implying all the runtime dll's aren't out tehre. I don't get that error because I have PB on my machine (i THINK). 

To clarify, i'm trying to create the pdf with a "save as" button on a datawindow that has returned rows (this in a custom app that has gone through many PB upgrades).  The app WILL allow me to save the return values to Excel but it will not save (or give an error) when saving as a PDF. This only works if I remove pbvm.dll and keep the older copy: PBVM170.dll. If I remove PBVM170.dll it won't work... If I have both it won't work. Or if I only have pbvm.dll it won't work. Any clues? I did rebuild the app in 32-bit (I just tried again even though that's the way i have consistently rebuilt it) - never tried 64-bit. 

Please share any details that might help!