1. Balaji Pinjala
  2. PowerBuilder
  3. Thursday, 31 May 2018 15:02 PM

We are using a Power Builder application which runs in Power Builder 12.1 version and it has PFC libraries in it. We need to migrate it to 2017 R2, we have already downloaded the latest PFC libraries from appeon website.

 
Do we need to migrate the existing code as it is (with the old PFC libraries) and then have to replace the new PFC libraries 
(or) 
Do we need to replace old PFC libraries with New ones first and then have to migrate it.
 
Please advise. Thank You.

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 11 June 2018 15:50 PM
  2. PowerBuilder
  3. # 1
0
Votes
Undo

If you plan on migrating your application to Powerserver WEB or Mobile, it might be a lot easier to NOT migrate to a newer version of PFC.

The new PFC's use lots of the newer powerbuilder types which aren't recognised by Powerserver (yet). There's an example that comes with powerserver web which uses a VERY old version of pfc's, but it works.

(I've tried to migrate to powerserver using the newer pfc's a few months ago (haven't finished) by creating my own version (basically taking out all of the types and functionality that we don't use and powerserver doesn't support). I'll pick that up again when I have some time.)

 

Comment
There are no comments made yet.
Kim Berghall Accepted Answer Pending Moderation
  1. Thursday, 31 May 2018 15:27 PM
  2. PowerBuilder
  3. # 2
0
Votes
Undo

Another suggestion. If you already don't have it, get Prodiff (formerly PBDelta). Then compare the old vs new PFC pbls and determine if the changes are okay. This step can be particularly difficult if your old version has a different set of header comments in each of the PFC scripts. We had to create a process to remove the header comments first in order to get a true delta compare. I wish they didn't put in those comments there because it makes delta compares very difficult. But other than that PFC is an amazingly good framework to use when building PB apps.

Comment
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Thursday, 31 May 2018 15:18 PM
  2. PowerBuilder
  3. # 3
0
Votes
Undo

Hi Balaji:

 

I would recommend you following these instructions:

 

  1. Backup all your source code.
  2. Do a full build of your current source code (including old PFC libraries).
  3. Optimize all your libraries.
  4. Migrate your current source code.
  5. Fix any errors that may come up after migration.
  6. Change PFC libraries to the latest ones.
  7. Fix any errors that may come up after PFC update.
  8. Do another full build.
  9. Re-optimize your libraries.
  10. Test!

 

I hope this helps.

 

 

Regards,

Comment
There are no comments made yet.
  1. Thursday, 31 May 2018 15:16 PM
  2. PowerBuilder
  3. # 4
0
Votes
Undo

You need to migrate you existing libraries to the new version (so with the old PFCs) and then replace the PCs with the new version libraries.

My guess is that the new libraries are already in version 2017R2 and so cannot be included in an older version of PB.

All the best

David

Comment
There are no comments made yet.
Kevin Ridley Accepted Answer Pending Moderation
  1. Thursday, 31 May 2018 15:15 PM
  2. PowerBuilder
  3. # 5
0
Votes
Undo

You may get differing opinions on this, but I would migrate first with the old  pfc, then replace with the new pfc and do a full rebuild.  You didn't mention extensions (PFE) so I'm assuming you don't have any pfc customizations.

Comment
We do have PFE's but we are not sure whether our application is having any customised code in extensions as its developed long back by a different team. Please suggest. Thank you.

  1. Balaji Pinjala
  2. Thursday, 31 May 2018 15:34 PM
You may have to ask around to see if there's a utility that you can use to scan your PFE objects to see if there is any code in them.  You probably already know this, but by default, the PFC comes with the PFC PBLs that contain all of the code, and PFE PBLs that are inherited from PFC but have no code in them (out of the box).  You then have the option to add code to the PFE objects that will extend the PFC code.  So you need to figure out if there's any code in there.  Maybe if you are using source control, you can do a DIFF between the old PFE objects and the new empty ones.  You could maybe try comparing file sizes.  If you have to check manually, I would start by looking at the PFEMAIN.PBL and inspect objects like u_dw, w_master, w_sheet, n_ds, u_tabpg.  You also may get lucky and it may find something in the rebuild when you replace the PFC/E with the new ones.  As always - TEST, TEST, TEST!!

  1. Kevin Ridley
  2. Friday, 1 June 2018 20:39 PM
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.