Hi, Albert -
Chris is correct.
A pfccom32.dll was distributed with early versions of the PFC to provide access to some of the Windows common dialog windows when there was no native PowerBuilder-supplied way to access them. If the version of the PFC you are using is referencing this deprecated and removed DLL, this tells me you are using a very old version of these libraries. The Platform Service probably also contains objects for other, non-Windows platforms, such as AIX, HP/UX, and the Solaris operating systems... and support for these platforms were also dropped from PowerBuilder a very long time ago.
It is (way past!) time for you to upgrade your version of the PFC libraries. Your old version of the PFC will not work with an app that is deployed to 64-bit, as Chris indicated. PFC releases compatible with PB 2019, PB 2021 and PB 2022 are available for download on GitHub:
https://github.com/OpenSourcePFCLibraries
Do not try to replace/swap only the PFCxxxxx pbl's, as this ill-advised, quick-and-dirty approach to PFC migration does not work. You need to replace all of the PFCxxxxx and PFExxxxx pbl's you have been using with new ones that are all from the same PFC version. If you have local modifications to any of the PFE-layer objects in your old, outdated version, you will have to examine those local modifications, analyze the code in the new version of the same object(s), and retrofit any modifications as appropriate. Hopefully, you have very few or none.
If you do not know if you have any local mod's to the PFE-layer objects, a simple (but slightly tedious) way to determine this is to Edit Source on every object in the PFE-layer pbl's... An un-modified/un-extended PFE-layer object will contain only a minimal amount of source code, as it will be an empty descendant of a PFC-layer object.
Good luck!
