Shared PBLs

Files in different Projects will be saved as separate entities in the Repository even if they were initially added from the same PBL. The result is that you have two different Repository entities updating the same PBL, which is not good.

What this means is that any shared files (PBLs) should be part of the same Project.

Second the directory structure in the Repository is going to reflect the directory structure of the Workspace/Targets relative to the “Local Root Directory” of the PowerBuilder Workspace. For example if the Root Directory is C:/source1 and a PBL is in that directory it’s objects will appear at the root of the Repository for that Project. If the PBL were in C:\source1\base, than the objects for that PBL would be in the ‘base’ subdirectory from the root of the Repository in the Project. I believe this is what is happening in your case 2. Although this imposes a restriction in how shared PBLs are structured, I believe this design is the only way to handle the objects with duplicate names.

So if you wish to share objects (PBLs) between Targets, then the rule is:

1. The Targets must be part of the same Workspace (PowerVCS Project).
2. The relative paths to the shared objects must be the same in each Target.

Phil