• You are here:  
  • Home
  • Q&A
  • Q&A
  • InfoMaker
  • Hospital needing help to convert a .pbl to an earlier version

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (10)

Resolved Hospital needing help to convert a .pbl to an earlier version

  1. How-to
0
Votes
Undo
  1. Shane Pilcher
    Shane Pilcher
  2. InfoMaker
  3. Thursday, 26 May 2022 17:49 PM UTC

We are a hospital using Paragon as our electronic medical record.  Paragon is only compatible with .pbl in version 2017.  We accidentally converted this file to 2021 and cannot run vital reports necessary to care for our patients. Is there a way to convert the .pbl back?

Undo Migration
New Database Connection using API Key
Accepted Answer
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Sunday, 29 May 2022 22:29 PM UTC
  2. InfoMaker
  3. # Permalink

As Mike said:

You will need someone with a PowerBuilder 2017 IDE to help you.
Since you are using InfoMaker I will assume that you do not have access to a PB2017 IDE.

Many of us here can do this for you, just reach out to someone and ask them to recompile the report. John Fauss might be the fastest.
HOWEVER: note that the report is in a PBL, and I'll bet the entire PBL was migrated, which means every report in it was migrated to PB2019.

So: reach out to someone on this forum and ask them to recompile the PBL in PB2017 <please tell us the build>.


Later -

Olan

PS: I can help with this, but I will need to install 2017 <build> on my PC and I am swamped in the real world so it might take me some time to turn the PBL around. I can but try if you ask.  Olan

Comment
There are no comments made yet.
Responses (10)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 26 May 2022 18:15 PM UTC
  2. InfoMaker
  3. # 1

You should just be able to regenerate the objects in 2017.

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 27 May 2022 16:53 PM UTC
  2. InfoMaker
  3. # 2

Any object that is NOT a datawindow can be regenerated.  

Datewindows that have been edited MUST be exported and the version number changed back to 17.  Then import the datawindow into your 2017 pbl.

 

your target should be recreated

 

 

 ** this only applies to recent versions of PB (2017,19,21).  older versions may need more work

Comment
Roland Smith
  1. Roland Smith
  2. Friday, 27 May 2022 17:35 PM UTC
He can do a search for 'Release 19' to find out which ones where changed.

  1. Helpful 2
There are no comments made yet.
Shane Pilcher
Shane Pilcher Accepted Answer Pending Moderation
  1. Tuesday, 31 May 2022 14:21 PM UTC
  2. InfoMaker
  3. # 3

Again, thank you all for your responses.  They have been extremely valuable.  We were able to restore from a backed-up copy. After final RCA, we determined it was not a result of not following procedures.  Instead, we inadvertently were editing and creating reports in the PROD pbl. We have since changed that process to make all changes in separate pbl file and move it into PROD when we are ready to publish the changes. 

Comment
John Fauss
  1. John Fauss
  2. Tuesday, 31 May 2022 14:53 PM UTC
That is great news, Shane! Thank you for letting us know how the issue was resolved.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Thursday, 26 May 2022 18:04 PM UTC
  2. InfoMaker
  3. # 4

As Chris explains here in this post from 90 minutes ago...

https://community.appeon.com/index.php/qna/q-a/undo-migration

There is no migration "undo". Chris's response describes your available options.

Comment
There are no comments made yet.
Matt Balent
Matt Balent Accepted Answer Pending Moderation
  1. Friday, 27 May 2022 15:55 PM UTC
  2. InfoMaker
  3. # 5

Hey, I used to work on that application (Paragon) while at McKesson.  Do you have another machine on your network with an 'un-upgraded' version of the .pbl?  Just copy it back from there.

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Sunday, 29 May 2022 07:10 AM UTC
  2. InfoMaker
  3. # 6

Hi,

Just now, I realized that you might not have a Powerbuilder IDE to re-convert to 2017. Since you're using "Infomaker".

If you want, I can try to convert the pbl for you. The only thing I would have to know is which build of 2017 the pbl was originally made with.

regards.

Comment
Andreas Mykonios
  1. Andreas Mykonios
  2. Monday, 30 May 2022 06:18 AM UTC
You can always use the initial release of PB 2017...
  1. Helpful 1
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 30 May 2022 07:40 AM UTC
Hi Andreas,

Yes you're right. It's only a PBL.

regards.
  1. Helpful
There are no comments made yet.
Christopher Craft
Christopher Craft Accepted Answer Pending Moderation
  1. Thursday, 26 May 2022 18:06 PM UTC
  2. InfoMaker
  3. # 7

Can you get it from the Windows 'Restore previous versions' feature? If not then you might be able to export all the objects from 2021 and then re-import them into the correct PBL version?  Never tried but could work since none of the syntax gets changed.

Lastly, not trying to pour salt onto a wound but if this is that critical then you should be using a source control system - you can restore anything at that point.

Chris Craft

Comment
Arnd Schmidt
  1. Arnd Schmidt
  2. Thursday, 26 May 2022 18:24 PM UTC
If this is only one PBL (without an application object) that should be done within an hour of time for an intermediate PowerBuilder Consultant as long as you did not any changes after the migration.

If it only includes untouched Datawindows .. trivial.

Arnd
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 May 2022 18:07 PM UTC
  2. InfoMaker
  3. # 8

If you didn't make any backup, one of our consulting partners might be able to help you salvage the code: https://www.appeon.com/consultants/consulting-partners

Comment
There are no comments made yet.
Shane Pilcher
Shane Pilcher Accepted Answer Pending Moderation
  1. Thursday, 26 May 2022 18:41 PM UTC
  2. InfoMaker
  3. # 9

Thank you for your responses.  We are locating that file in our backups.  Unfortunately, it seems our policy and procedure was not followed which would have created a copy of that file at the time it was replaced. I appreciate your help!

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 26 May 2022 19:56 PM UTC
Hi,

You can simply export all of the objects and re-import them into a pb2017 library. If you have modified datawindow objects, you export them and then edit them first. On one of the first lines you have to change "release to be 17" instead of 21. I don't think you might have to delete any 'new' attributes of the exported dw source, but you might. I havent tried it with 2021 myself yet.
  1. Helpful 1
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.