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

Resolved migrating two main PBLs

  1. How-to
0
Votes
Undo
  1. Lorna Vargas
    Lorna Vargas
  2. PowerBuilder
  3. Tuesday, 10 November 2020 16:45 PM UTC

Good morning,

The application I am trying to migrate contains two main PBLs.  The scms.pbl has objects (exe file).

 

The second PBL (jyw.pbl)  doesn't seem to have any objects. Once we selected and click Next, it will follow with an error message. This PBL contains windows that are used for the application.  do you know any solution to migrate the below PBL?

Note: Other PBLs shown in the screenshots are backups.  please ignores them.

Thanks for your help

Calling PFC_Copy from Ribbonbar
RestClient and Integrated Windows Authentication (...
Responses (2)
Lorna Vargas
Lorna Vargas Accepted Answer Pending Moderation
  1. Wednesday, 11 November 2020 01:48 AM UTC
  2. PowerBuilder
  3. # 1

Hi John,

 

My purpose is to migrate all PBLs at once. However, the second pbl (jyw.pbl)  seems not to have an application object. Therefore, it won't go forward with the migration.  I am hoping to find a solution within Appeon community. Unfortunately, this is how the application was built and passed on to me as is.

 

Your help will be greatly appreciated.

 

Lorna

Comment
John Fauss
  1. John Fauss
  2. Wednesday, 11 November 2020 04:56 AM UTC
There has to be an Application Object...if it's not in the jyw.pbl, it has to be in another pbl that is also part of that application.

You have to select the pbl that contains the application's Application Object in order to migrate the application to a newer version. There's no way around it, at least that I know of, and I've been using PB since version 4.

It sounds like you need to open the set of pbl's that the jyw.pbl is a part of using the version of PB it was developed in, inspect the pbl's to identify the one that contains the application object, then open that library in the new(er) version of PB.
  1. Helpful
John Fauss
  1. John Fauss
  2. Wednesday, 11 November 2020 15:15 PM UTC
The primary reason the Application Object is required in order to perform a version migration is this is where the declaration for global variables, global types (the SQLCA transaction object, the Message object, etc.) and the application icon all reside.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 10 November 2020 19:26 PM UTC
  2. PowerBuilder
  3. # 2

Hi, Lorna - 

I believe the purpose of this dialog window is to identify both the library (PBL) and application object (as the name of the dialog window states), not simply a library. Version migration is performed on all of an application's libraries at once, so this can only occur when an application object (and the library that contains it) is identified.

HTH, John

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 12 November 2020 19:58 PM UTC
Also, you should NEVER have two or more Application Objects in any combination of PBL's for a PB App. That is a "PB No, no"!
  1. Helpful
Andrew Barnes
  1. Andrew Barnes
  2. Thursday, 12 November 2020 22:43 PM UTC
Depending upon your situation, it does not cause a problem. We have beta and production versions of our applications, each using a separate application object with the app objects for each in the application's main PBL. One of our application has two versions with a beta and prod as well for a total of four application objects in the main PBL. We have been doing that for 20+ years. It has never caused an issue, either for program development, application building, or PB version migrations starting with PB5 through PB2017R3.
  1. Helpful
Lorna Vargas
  1. Lorna Vargas
  2. Tuesday, 1 December 2020 07:27 AM UTC
thanks for the info. the issue was solved.
  1. Helpful
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.