Great info, thank you guys.

We rely heavily on pfc. After knowing the different challenges of going to 64 bit, I'm pretty sure 'the powers that be' will reconsider the move.

Hi Darren,

There are customers using PFC in 64-bit.  To best of my knowledge, there are only two areas of PFC that currently are not 64-bit compliant.  So only if you are using these you may need to adjust that part of the PFC code:

• n_cst_environment – API Call: GetVersionEx
• n_cst_filesrvunicode = API Call:  OpenFile – Used by the setlastwritedatetime and setcreationdatetime functions

I agree with John, first do a simple test case with the latest PFC libraries using either PowerBuilder 2017 R3 or 2019 R2: https://github.com/OpenSourcePFCLibraries

Assuming the latest PFC's work fine, after switching out your PFC libraries with the latest one, then follow through this presentation to make the rest of your app compliant: https://www.appeon.com/developers/library/videos/migrating-powerbuilder-desktop-apps-64-bit.html

Regards,
Armeen

Hi Darren;

  Here is a question for the PFC community in general as even I do not know the answer to this ...

Is the PFC Framework 64bit complaint?

Regards ... Chris

Hi, Darren - 

What is the rationale for needing to produce 64-bit executables (aside from Pointy-Hair Boss tells you to)?

From the information contained in your question, it appears your app(s) are based on the PFC. As you probably know, the PFC was created 20+ years ago, WA-A-A-AAAAY before 64-bit operating systems came into being. What version of the PFC libraries are you using ... have they been updated recently?

The PFC utilizes some Windows API calls, and the rules for interfacing with WinAPI functions can be a little different in a 64-bit environment, depending on each particular API function. As far as I know, there is not currently a version of the PFC libraries that is designed to be 64-bit compatible. This is unfortunate, but because it has been Open-Source'd for several years, I do not see this changing anytime soon.

My advice is to start small. Create a very simple, single-window, non-MDI application based on the latest set of PFC libraries, then successfully create a 64-bit version of this test app. If your apps make use of the some of the PFC features that interface with the Windoes API (file-related functions, for example), then methodically expand the test app to include use of these features. Then try a simple MDI app. Learn from the experiences what may be required in order to migrate one of your "real" apps. You may find that this is going to require substantially more effort than management wants to spend for whatever benefits are to be gained. Test the waters before jumping into the shark pool.

Regards, John