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.

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

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.

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

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

Olan

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