1. Samir Kothari
  2. PowerBuilder
  3. Friday, 20 July 2018 20:14 PM UTC

Hello,


We are about to start migrating our Power Builder Application('s) Classic 12.5 to Power Builder 20017 R2. They all contain PFC \ PFE's version 5.

Not only do we have modified PFE's, but PFC's ( I know ).

Should I download the PFC libraries for 2017, manually make the changes to this, by copying the old pfc and pfe code changes and apply them to the new pfc/pfe objects or is there an alternative/easier approach?

Does there happen to be any documentation on obsolete items?

Just trying think of the best strategy on migrating all 6 company applications.

Thanks

Sam

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 16:43 PM UTC
  2. PowerBuilder
  3. # 1

Hi Samir;

  Hopefully, this PFC summary of changes might help ... http://www.pfcguide.com/news/whatsnew.asp

Regards ... Chris

Comment
There are no comments made yet.
Samir Kothari Accepted Answer Pending Moderation
  1. Thursday, 26 July 2018 16:11 PM UTC
  2. PowerBuilder
  3. # 2

Thank you all for your comments, I did find them very useful.

I'm going to try and see if the changed PFC in my old libraries can be implemented in the new PFE objects

I suspect my main challenge is dealing with obsolete/changed objects between my old pfc library and the new library. Which leads me to the following question:

Does anyone no where I can find any kind of documentation that will help me identify changes or obsolete pfc/pfe object/functionality between version 5 and any versions above 9 (ideally pfc 2017).

Comment
  1. Armeen Mazda @Appeon
  2. Thursday, 26 July 2018 20:33 PM UTC
  1. Helpful
  1. Samir Kothari
  2. Wednesday, 1 August 2018 17:55 PM UTC
Thanks, but couldn't see anything related to pfc/pfe migration
  1. Helpful
There are no comments made yet.
Kevin Ridley Accepted Answer Pending Moderation
  1. Monday, 23 July 2018 12:42 PM UTC
  2. PowerBuilder
  3. # 3

IMHO the answer is - it depends.  First, I would do as Gerry said and migrate your current PFC/E and try that out.  Make a backup before and after.  If it works, decide if you need any of the new functionality.  If you are using the version 5 PFC, you don't have any of the unicode or platform specific code.  It mostly depends on how long you think the application(s) will be around.  For maintainability, it's always best to be on the current version, and again, you may need to add some unicode functionality or use the platform services going forward.

 

If you know what PFC objects were changed, you could try doing this:

1) Make backups!

2) Download the new PFC/E and overlay the PFE with your changed ones.  Depending how many changes there were, you might want to go object by object instead of full PBLs.

3) See if the changed PFC in your old libraries can be implemented in PFE objects instead, and do that.

4) Regen, optimize and test.

 

Evaluate the PFC/E changes.  If they were made in version 5, there's a pretty good chance whatever was being "enhanced" could be taken care of in a newer version.  You could even try just using the new PFC/E and seeing what breaks in testing, and evaluate from there.

 

Good luck,

Kevin

Comment
There are no comments made yet.
Gerry Whitmarsh Accepted Answer Pending Moderation
  1. Saturday, 21 July 2018 07:39 AM UTC
  2. PowerBuilder
  3. # 4

Hi,

I am running PB 2017 R2 and am still using the pfc version 10.5 with no problems. If it ain't broke, don't fix it is my motto.

My 2c.

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 20 July 2018 22:40 PM UTC
  2. PowerBuilder
  3. # 5

Bruce Armstrong has a set of PFC files that have already been migrated for PB2017.

https://github.com/OpenSourcePFCLibraries

 

Olan

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.