Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Deploying application to users

  1. How-to
0
Votes
Undo
  1. Lorna Vargas
    Lorna Vargas
  2. PowerBuilder
  3. Friday, 12 February 2021 02:33 AM UTC

Hi,

 

I am able to run the application (PowerBuilder 2019 R2) on my pc.  however, once I copied the pbd and exe file on the user's pc and try to open the application, I get a system error message (screenshot below).  I read the Deployment documents and I am still puzzled. So my questions are the following:

1) if I Build and Deploy pointing to the C drive on my pc . Does that mean I have copy the pdb and exe file on the user's pc pointing to c drive?

2) the Deployment documents refers a Runtime Packager. Do I need to run it before I deploy the application to the user?

Your help will be appreciated.

 

Lorna

 

 

 

  1. Deployment
Powebuilder ans SQl server compatibility
How to debug the PowerServer client app that runs ...
Responses (2)
Lorna Vargas
Lorna Vargas Accepted Answer Pending Moderation
  1. Friday, 12 February 2021 22:42 PM UTC
  2. PowerBuilder
  3. # 1

Thanks for the feedback.  We ended up running the PowerBuilder Runtime Package and follow the instructions from the link https://docs.appeon.com/pb2019/application_techniques/ch35s02.html . Then we copy the MSI file created from the Runtime Package on the user's pc.  Ran it, install it and ran the executable with no issues.

 

 

Lorna

 

Comment
John Fauss
  1. John Fauss
  2. Friday, 12 February 2021 23:02 PM UTC
Good to hear you have a solution that works for you, Lorna. Thanks for letting us know!
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 12 February 2021 03:32 AM UTC
  2. PowerBuilder
  3. # 2

Hi Lorna,

1) No, not necessarily, but the application will run faster if installed/copied on the local hard drive of the user's PC.

2) It doesn't matter if you install the powerbuilder runtime before or after, but you have to:

2A- Install  the pb runtime on the user's pc. The runtime "packager" allows you to create an MSI installer for the needed powerbuilder runtime files. The result can be used to install the runtime on the user's pc. 
or ...
2B- copy all the needed runtime dll's and files somewhere to a folder which is in the PATH
or ...
2C- copy all the needed runtime dll's and files to the folder where the EXE is (in your case on drive V:\SCMS2019. This last option only works if after any file operation (like fileopen(), etc.) of using GetFileSaveName() and similar functions, you will have to set the "current windows directory" back to where the EXE is, using ChangeDirectory().

If you can, I recommend installing (2A) the runtime and make sure there are no older runtimes already installed. (install those first if the user no longer needs them for older (other) applications).

regards,

Miguel

PS: What I do personally:
I have no runtime install and no fixed PATH changes.
What I have is:
- a shortcut to the exe on my desktop. The shortcut's "start in" ("inicio en") points to where the pb runtime folder is.
- In the application object's Open event, I modify the PATH variable to be preceded with the path to the Runtime, followed by whatever was in the path already (so not fixed in windows itself, but from my code).
This will change the path, but only for the running powerbuilder application's session. Other applications like word or excel won't see that change of the path.
This allows us to be able to have older and newer applications on the same machine, using different runtimes without conflicting with eachother.

saludos

Comment
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.