I have built a very simple PB application. I can deploy it as a 32-bit application with no trouble. For 64-bit I just change the project setting to 64-bit, rebuild and redeploy with the EXE to be written
to the x64 PowerBuilder Shared directory.
When run, the application briefly (sub-second) shows the window and then shuts down.
I've also tried the run-time packager with the same result. What am I missing?
Any help appreciated....Phil
-
Phil Wallingford
- PowerBuilder
- Wednesday, 14 November 2018 22:23 PM UTC
Comment
- Phil Wallingford
- Thursday, 15 November 2018 20:51 PM UTC
Thanks for chiming in Roland.
It's a simple Hello World application (the limit of my ability) and no DB.
I tried creating the EXE in the Shared/PowerBuilder/x64 directory figuring it would have the best chance of working. The I created a Run-time Package but still no luck.
Phil
It's a simple Hello World application (the limit of my ability) and no DB.
I tried creating the EXE in the Shared/PowerBuilder/x64 directory figuring it would have the best chance of working. The I created a Run-time Package but still no luck.
Phil
There are no comments made yet.
Comment
- Chris Pollach @Appeon
- Thursday, 15 November 2018 14:47 PM UTC
Sounds like any other development environment.
I have not had any problems compiling to 64bit since PB12.6 introduced the feature. However, you may need to adjust your App(s) for 64bit external DLL's, DB drivers, SDK calls etc.
If a simple "Hello World" 64 bit App though does not work, then it could be because:
1) The 64bit PB run-time is not is the O/S System Path
2) You did not deploy the 64bit run-time using the Packager utility.
I have not had any problems compiling to 64bit since PB12.6 introduced the feature. However, you may need to adjust your App(s) for 64bit external DLL's, DB drivers, SDK calls etc.
If a simple "Hello World" 64 bit App though does not work, then it could be because:
1) The 64bit PB run-time is not is the O/S System Path
2) You did not deploy the 64bit run-time using the Packager utility.
- Phil Wallingford
- Thursday, 15 November 2018 20:54 PM UTC
Thanks, Chris.
Shouldn't creating the EXE in the x64 Shared directory give it access to everything it needs?
I'm going to try this another machine and see if the problem persists. I went through with TeamViewer with a PowerGen customer and had no trouble on his machine.
So probably something awry with the PC I've been using?
Shouldn't creating the EXE in the x64 Shared directory give it access to everything it needs?
I'm going to try this another machine and see if the problem persists. I went through with TeamViewer with a PowerGen customer and had no trouble on his machine.
So probably something awry with the PC I've been using?
There are no comments made yet.
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.
Regards,
Phil
I am leery to say this but, I wonder if reinstalling PB2017R3 might be the answer? I have never had issues with my 64bit App compiles in PB2017 GA, R2, or R3 releases on my W10 PC's. Your lack of compiling any simple PB App into a to 64bit EXE is most concerning (and certainly not normal).
PS: Have you tried running the PB IDE and/or your PB App EXE in "ADMIN" mode (as an interest)?
Regards ... Chris