1. Jeffrey Alonzo
  2. PowerBuilder
  3. Thursday, 15 November 2018

Hi Gurus,

 

We have a couple of applications that needs to be migrated to PB2017 and discovered that it has 3 sets of PFC libraries on its workspace.  Honestly, I have not seen any tool that is available online that can create PFD files from PFC.

In the past, these was a PFC extender in PB6 or PB7 - I could be wrong though.  I see old posts from other forums but not much help.

Any advise is deeply appreciated.

Thanks,

 

Jeff

Ronnie Po Accepted Answer Pending Moderation
0
Votes
Undo

Earlier versions of PowerBuilder (6.5, I believe, and maybe others) included a PFC "extender" tool which automatically created a layer between the pfc_ and pfe_ layers.

Comment
Yes, there was.

That utility was deprecated shortly after that release though.
  1. Chris Pollach @Appeon
  2. Saturday, 17 November 2018
There are no comments made yet.
  1. Friday, 16 November 2018
  2. PowerBuilder
  3. # 1
Kevin Ridley Accepted Answer Pending Moderation
0
Votes
Undo

You have a lot going on here.  Just a few questions and some suggestions/options for you at the end.  How many objects actually have code in the PFD layer?  Is it feasible to go through the PFD and see what kind of functionality is in there?  You may be able to put that functionality into the PFE layer instead and eliminate the PFD completely.  Is there additional extensions in the PFE?  If there's no code in the PFE, you can always just move the PFD code to the PFE and then eliminate the PFD.

Here's something else that might work:

1) Backup EVERYTHING!

2) Setup 2 targets - 1 existing app, 1 with new PFC/E (easier to copy objects)

3) In your app target, use the NEW PFC PBLs with your existing PFD and PFE

4) Do a full build and fix errors for new objects / obsolete

5) Add any PFE objects that are new in PFC

 

Lmk how it goes or if you need additional advice.

Kevin

Comment
There are no comments made yet.
  1. Friday, 16 November 2018
  2. PowerBuilder
  3. # 2
Olan Knight Accepted Answer Pending Moderation
0
Votes
Undo

As long as the app compiles, yo uare golden. Your inheritance chain is intact, so:

     application PBLs   <--  PFE PBLs  <--  PFD PBLs  <--  PFC PBLs


When we created a CORP layer, we had to manually add the new layer into the code.

I am not aware of a took that will do this for you, but it should be easy enough to write a quick app that looks at the EXPORTED files from your PFE and to overwrite the inheritance from PFC to PFD.

 

1. Export the contents of the PFE PBLs.

2. Run the app to change the inheritance from PFC to PFD

3. If the PFD PBLs are already inderiting from the PFC, you are good to go.
    If not, then tweak the app you just wrote to update the exported files of the PFD.

4. Import the exported files into a new, separate, not to screw up the original code set of libraries

5. compile.

 

The main issue I see is with obsolete objects.

 

Good Luck,

Olan

Comment
There are no comments made yet.
  1. Friday, 16 November 2018
  2. PowerBuilder
  3. # 3
Roland Smith Accepted Answer Pending Moderation
0
Votes
Undo

Since the PFD*.PBL files already exist in the version of PowerBuilder you are currently using, what exactly is the problem?

Comment
Hi Roland,



I'm looking for a way(faster) to extend PFC 2017 libraries as PFD and not as PFE, We have a process on comparing PFC libraries (old version vs. new version), I have no way to compare PFD*.PBL files and have thought about just skipping this compare process for PFD*.PBL files and just regenerate these during the migration.



regards,



Jeff
  1. Jeffrey Alonzo
  2. Thursday, 15 November 2018
There are no comments made yet.
  1. Thursday, 15 November 2018
  2. PowerBuilder
  3. # 4
Jeffrey Alonzo Accepted Answer Pending Moderation
0
Votes
Undo

Hi Chris,

 

I updated my post.  Looking for a PFC Extender that I can use to extend PFC 2017 libraries to PFD.  We have 2 applications where PFC libraries have PFD layer in its workspace.  So instead of the normal PFC and PFE libraries, there is another one which is PFD.  PFE libraries were inherited from PFD libraries.

 

Regards,

 

Jeff

Comment
Ahhh ... my guess is that this might be a set pf PBL's with your own file type naming convention (weird) that represent a "Corporate" extension layer. The PFE layer could have been edited to point to a set of Corporate ancestors that in turn point to the PFC layered ancestors.



Still strange though using the .PFD file extension vs ".PBL". :-(
  1. Chris Pollach @Appeon
  2. Thursday, 15 November 2018
The PFD are still PBLs. So, like pfdapsrv.pbl is inherited from pfcapsrv.pbl and pfeapsrv.pbl is inherited from pfdapsrv.pbl. The PFD layer might have been the PFE layer that was renamed, I don't know because these are 15+ year old apps. Just trying to look for a quicker way to have a PFC 2017 PFD layer.



  1. Jeffrey Alonzo
  2. Thursday, 15 November 2018
There are no comments made yet.
  1. Thursday, 15 November 2018
  2. PowerBuilder
  3. # 5
Chris Pollach @Appeon Accepted Answer Pending Moderation
0
Votes
Undo

Hi Jeff;

  Well I am totally confused. To me PFD means Personal Flotation Device (LOL) but, I assume that as a file type it could be related to a PlayStation file, Planning Force, Proform, iGrafx, etc software. All to which I have no idea what that could be used for in a PB App (or the PFC for that matter).

  Can you give us more details / context?

Regards ... Chris

Comment
There are no comments made yet.
  1. Thursday, 15 November 2018
  2. PowerBuilder
  3. # 6
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.