1. Ganesan Rajan
  2. PowerBuilder
  3. Monday, 13 May 2019 12:07 PM UTC

Hi,

We have an application in Powerbuilder 12.0 and also the same application migrated to Pb2017. Now we maintain two versions of application and of course the latest version (using PB2017) has more functionalities to meet our customers' requirements.

Our application is installed using MSI.

Step 1: Install Application1 (PB12 one) in a path C:\ProgramFiles(x86)\Prod\Exe. This folder will have .exe and .pbd files.
MSI will create an another folder C:\ProgramFiles(x86)\Prod\Shared where it copies all shared PB12 libraries which is necessary to run the application.

Able to run the Application1 without any issues.


Step 2: Install Application2 (PB2017 one) in same machine in different path say C:\ProgramFiles(x86)\Application2\Prod\Exe.

MSI will create an another folder C:\ProgramFiles(x86)\Application2\Prod\Shared where it copies all shared PB2017 libraries which is necessary to run the application.

Able to run Application2 without any issues.


PROBLEM: Now If I try to run Application1.exe, I am getting "The program can't start because PBVM120.dll is missing from your computer. Try reinstalling the program to fix this problem"

Whatever the latest MSI is run, that application works fine. But another one fails.

Also we are not supposed to copy PB libraries in respective EXE folders.

Can you please throw some light on why this issue occurs?

Note: PB is not installed in the machine used for this testing.

Thanks,

Ganesan R

Roland Smith Accepted Answer Pending Moderation
  1. Monday, 13 May 2019 12:55 PM UTC
  2. PowerBuilder
  3. # 1

The program may be depending on the AppPath setting in the Registry to find the runtime dll files.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\myprogram.exe

 

If that is the issue, you could change the name of the exe for the PB12 version.

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Monday, 13 May 2019 13:49 PM UTC
  2. PowerBuilder
  3. # 2

just install everything in one directory.   the shared directory approach is just causing problems and more work and provides zero benefit.

 

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 13 May 2019 18:30 PM UTC
  2. PowerBuilder
  3. # 3

Hi Ganesa;

  Just create either a .BAT file that starts you PB App's EXE or an O/S short-cut for each. In the Bat/Short-cut ... point to the App's "Start in" folder. That should restrict where the O/S searches for the PB run-time DLL's and most importantly what location of the EXE is PB12.x vs 2017Rx.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 14 May 2019 18:56 PM UTC
  2. PowerBuilder
  3. # 4

What Mike S said.
Why bother with anything more complex?

Olan

 

Comment
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Wednesday, 15 May 2019 10:57 AM UTC
  2. PowerBuilder
  3. # 5

Hello,

Add both folders (C:\ProgramFiles(x86)\Prod\Shared    &  C:\ProgramFiles(x86)\Application2\Prod\Shared )  to PATH environment variables and see the result.

Happiness Always
BKR Sivaprakash

 

 

Comment
There are no comments made yet.
Ganesan Rajan Accepted Answer Pending Moderation
  1. Monday, 20 May 2019 12:10 PM UTC
  2. PowerBuilder
  3. # 6

Thanks Roland. I shall check and get back.

Comment
There are no comments made yet.
Ganesan Rajan Accepted Answer Pending Moderation
  1. Monday, 20 May 2019 12:12 PM UTC
  2. PowerBuilder
  3. # 7

Hi Chris, Thank you. I shall check and get back.

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.