1. Adrian Parker
  2. PowerBuilder
  3. Sunday, 22 April 2018 12:03 PM UTC

Just migrated our application from 11.5, with no errors.  During the migrate, I changed the pbdom115 library entry to pbdom170 and that's fine.   The problem I now have is that when I try to deploy the applications I get an error due to the project library list still contains a reference to pbdom115..  it says..

"The current library list is different from the library list contained within this project. The project library list has been updated. Refresh build options for the changed list and try "

Going into the project, it still shows the old entry, but there doesn't seem to be a way of fixing it..  I've done full builds etc, but it doesn't seem to make a difference.

Only way I can seem to do it is to delete and recreate the project for each target in the workspace.


Accepted Answer
Kim Berghall Accepted Answer Pending Moderation
  1. Sunday, 22 April 2018 20:10 PM UTC
  2. PowerBuilder
  3. # Permalink

I think when you get the message you indicated, you just save and perhaps check the "PBD" boxes as needed. Then it should have the correct libraries when you try to build again.

  1. Adrian Parker
  2. Sunday, 22 April 2018 22:52 PM UTC
Yes, tried that and it didn't make a difference.

I have exported the projects for all targets and corrected the library entry and re-imported the project..   now it builds all targets with no errors, but for one of the targets it doesn't create any PBDs or EXEs..    pb11.5 builds fine, just not in 17r2

  1. Helpful
  1. Michael Kramer
  2. Sunday, 22 April 2018 23:52 PM UTC
Hi Adrian,

Changing the library list of a deployment project is a multi-step process:

Open your deploy project in the Project Painter - it contains the library list from last time it was deployed (i.e. it contains the file PBDOM115.PBD) despite your PB Target containing a different library list

Deploy your project inside the Project Painter. This will fail when library list is updated.

​HOWEVER: The library list inside your deploy project has been updated to match your PB target's library list

Verify that the PBD checkmark is set for all relevant PBL/PBD files.

SAVE your deploy project

Deploy your project once more. NOW deploy should succeed and generate PBD file for each PBL/PBD having a PBD checkmark!

SAVE your deploy project again.


HTH /Michael

  1. Helpful
  1. Adrian Parker
  2. Monday, 23 April 2018 07:58 AM UTC
I reverted the projects to my old 115 version and you're right about the project being corrected after attempting to deploy after first attempt.   I'll create another post about PBD/EXEs not being created for the target as that's still happening.

  1. Helpful
There are no comments made yet.

There are replies in this question but you are not allowed to view the replies from this question.