Powerbuilder 7 In Windows 7

[rolan181]

Hi,
My company is in the process of migrating from Windows XP to Windows 7. As this is the case, our Powerbuilder 7 applications are getting moved as well.

We've gotten builds of the applications (from xp) working on the windows 7 machines, but we're having issues when trying to run the applications from the powerbuilder IDE.

In windows 7 when I log into a user schema (ex: 'BMP') when running the application, the calls to public functions get prepended with the user schema name. This looks something like:
bmp.sf_return_app_version

what should be called is:
sf_return_app_version


The database hasn't changed, the PB version hasn't changed, the only thing (to my knowledge) that has changed is the Operating system. Why would the schema name be added before the function call in Windows 7?

Do you know what could be causing this error?

Thanks

 

[rolan181]

The fix is something of a workaround.

I ended up copying the PBO8470.dll file from the soms application installed into the PB7 Shared folder, replacing the one installed by Powerbuilder.

In comparing the two files, it seemed that the binaries had been compiled differently on each machine, but windows 7 had the ability to interpret the binary compiled on the windows xp machine.

I'd attach a copy here, but there doesn't seem to be a file upload area.

In any case, If you can find a copy of that dll from a previous version of windows, and replace the one installed on the machine, it should work.

 

[rolan181]

Just as an added sidenote, you can copy an existing install in winxp (including registry items) straight to windows 7 and it works. I'm not sure how stable an xp program is on a windows 7 machine, but it works.

 

[AshishGhildiyal]

I was involved in PB app migration in one of my projects. We verified the app exes in both 32-bit and 64-bit folder in Win7. They worked fine.
Just make sure if there is any hard coding involved pointing to C:\Program Files. As in Win 7, we have C:\Program Files(x86). Reference to particular directories might create issue. We fixed this by using GetCurrentDirectoryA() function.

-----------------------------------------------
Ashish

http://powerbuildernotes.blogspot.in/