Firstly my original question link regarding PB 10.5 on windows 7 64-bit has been mostly answered in the following link - Has anyone had any experience with PB 10.5 runtime files on a 64 bit machine? Currently have a 32-bit application on Windows XP. Client wants it working in Windows 7 64-bit.

PowerBuilder 12.0 PowerBuilder 10.5 PowerBuilder 9.0.2.7578. And.NET platforms. This rapid application development (RAD) software makes the construction of prototypes fast. It has a native data-handling object (data window), which is used to create, edit, and display data. Informer Technologies, Inc.

I know this is a big jump and PB 10.5 has been unsupported for a long time now. Has any one successfully fooled around with The Runtime Packager PowerBuilder runtime DLLs and got any of the following DLL's wokring in a Windows 7 64-bit system? Libjcc.dll libjutils.dll pbacc105.dll pbdwe105.dll pbdwr105.dll pbdwr105.pbd pbjag105.dll pbjvm105.dll pbshr105.dll pbtra105.dll pbvm105.dll I realize these are 32-bit DLL's but I need to start somewhere and not sure how to tackle this one. Hoping for anyones help or advise. Debuggin the app has been a bit of challenge only because of the environment setup for us isn't working perfect.

We have a virtual machine with Windows 7 64bit. Installed PowerBuilder 10.5 on it. It actually runs.

However trying to debug the app from this point yeilds all kinds of issues. One of them is each window with a datawindow is completely blanks, no feilds, nothing. I have not tried to run your above suggestion so I will look at that.

Someone had also suggested possibly running the application with a /DEBUG swicth from a command line. Then looking at the output through PBL Peeper. – Apr 3 '13 at 17:11 •. I suspect the most useful answer to you is a completely useless answer. First point is that PB 10.5 pre-dates Windows 7. Very obviously, any success of 10.5 on Windows 7 is going to rely on Microsoft's ability to provide forward compatibility of applications. (MS's success with providing forward compatibility is stellar compared to other platforms I've used, but has never been perfect.) Windows 7 was released around the PB 11.0 time frame, IIRC.

It took Sybase to somewhere in the 12.0 cycle to announce that they would support Windows 7. Support for a new platform is a good feather for your marketing cap, so a reasonable interpretation of this delay is that they found some issues and had to work them out.

Inf allos 9.2.2.1034 pv. (To the best of my knowledge, Sybase never listed those issues in one place, although some probably show up in the bug lists published with each patch.) I'm going to go out on a limb and bet that if you created a 10.5 application with one line in the application Open event: MessageBox ('Hello World!' ) and deployed this to Windows 7, it would work.