1. Bala Kotha
  2. PowerBuilder
  3. Monday, 07 October 2019

Hello All !!!

Last Friday, i have downloaded the PB 2019 30-Day Trial Version and installed standard edition and added my workspace and target but today when i am trying to open the same target in my current version v10.2 it says it "Could not add target because the target could not be created". can somebody help me with this ?

Please find the attachment which has the screenshot of the error message.

Attachments (1)
Roland Smith Accepted Answer Pending Moderation
0
Votes
Undo

The solution Miguel gave will work. It is really the only way to recover without restoring from a backup or source control copy.

Comment
There are no comments made yet.
  1. Tuesday, 8 October 2019
  2. PowerBuilder
  3. # 1
Olan Knight Accepted Answer Pending Moderation
0
Votes
Undo

What Michael said: ALWAYS ALWAYS ALWAYS work off of a copy of the original source code.
Always.

Olan

Comment
There are no comments made yet.
  1. Monday, 7 October 2019
  2. PowerBuilder
  3. # 2
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Bala;

   Once you migrate or create a new WorkSpace / Target in a higher PB version - the lower PB IDE's will not be able to utilize it. Its been that way since PB v1.0 => 2.0

Regards ... Chris

Comment
There are no comments made yet.
  1. Monday, 7 October 2019
  2. PowerBuilder
  3. # 3
Miguel Leeuwe Accepted Answer Pending Moderation
1
Votes
Undo

1) Create a new application target in PB10.2 in a different folder as where your migrated one is.

Use a new application, no template. Give that application the same name as the one you migrated.

2) Rename the "old", migrated to 2019 pbl where you application is: If your application was let's say "app.pbl" just make it "app2.pbl". Add all you "old" migrated libraries to the new pb10 target's library list, including the renamed pbl (eg."app2.pbl")

3) from the library painter, copy the objects of the renamed "app2.pbl" to the new "app.pbl" which you made in pb10.2.

4) unhook the app2.pbl from the library list (by editing the library list and removing the "app2.pbl")

5) do a full build of everything

 

If you have modified datawindows after having them migrated to 2019, the "release" info in their exported code will be "release 19". You will have to change that by exporting, editing and importing. Also there will be certain new attributes of the 2019 datawindows which did not exist at the time of 10.2. You will also have to delete those manually.

 

I you only migrated and did not change datawindows, then probably the old release info has not been changed.

 

Comment
There are no comments made yet.
  1. Monday, 7 October 2019
  2. PowerBuilder
  3. # 4
Michael Kramer Accepted Answer Pending Moderation
2
Votes
Undo

Hi Bala,

When migrated to newer version your PB files are no longer accessible from earlier PB version. Never were.

Solution: Revert to version you still have elsewhere in your file system, in version control, or on backup.

Rule of thumb when testing new version of any development tools
ALWAYS take COPY of development files (For PB: PBWs, PBTs, PBLs, PBDs, etc.) and migrate the COPY not the "live" version.

HTH /Michael

 

Comment
There are no comments made yet.
  1. Monday, 7 October 2019
  2. PowerBuilder
  3. # 5
Miguel Leeuwe Accepted Answer Pending Moderation
0
Votes
Undo

When opening a target in Powerbuilder, if it's from an older version, it will be migrated to the newer PB version.

After that you cannot open it again with the older version.

Comment
Is there any other way where i can open the same .pbt in the older version ?

like by downloading from source control or as such ?
  1. Bala Kotha
  2. Monday, 7 October 2019
There are no comments made yet.
  1. Monday, 7 October 2019
  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.