Before you can run your PowerBuilder Version 1.0 applications in Version 2.0, you must migrate the application to 2.0. 

When you migrate an application, PowerBuilder migrates all the libraries on the library search path. 

TIP:   If a library contains more than one application, PowerBuilder references to global variables that are not in the current application will cause a compiler error.  If this occurs, continue migrating the application and when the migration is complete, change the current application and run migration again.

Gupta SQLBase users:

The first time you connect to an SQLBase database, Version 2.0 reformats the extended attribute information in that SQLBase database.  After this occurs, Version 1.0 will no longer find extended attributes.  Therefore, you may want to make a copy of your SQLBase database before you connect to it in Version 2.0.

Preparation

Before you migrate your applications, you should:

Make a back up copy of the application libraries.

Check the scripts in the application to make sure you are not using these new reserved words as variable names.  If you use these words as variable names, they will cause compiler errors.

Procedures

You can use any of the following procedures to migrate an application:

Procedure 1

If when you signon to Version 2.0 of PowerBuilder the default application is a 1.0 application that you have not migrated to Version 2.0, PowerBuilder displays a message asking whether you want to migrate the application to Version 2.0. 

Click OK to migrate the application.  PowerBuilder displays the Migrate Application From 1.0 to 2.0 window.  See step 2 in Procedure 3.

Procedure 2

If are working in Version 2.0 and want to use a 1.0 application that has not been migrated:

1. Open the Application Painter by double-clicking the Application Painter icon in the Power Panel
2. Select the application you want to migrate and make it the default application.  PowerBuilder displays a message asking whether you want to migrate the application to Version 2.0. 
3. Click OK to migrate the application. PowerBuilder displays the Migrate Application From 1.0 to 2.0 window.  See step 2 in Procedure 3.

Procedure 3

1. Open the Library Painter by clicking in the Library Painter icon on the Power Panel.

Note: If the current application is not in the directory that contains the application you want to migrate, open the Application Painter and make an application in that directory the current application.

2. Select the application you want to migrate.
3. Select Migrate From 1.0 to 2.0 from the Utilities menu.  The Migrate From 1.0 to 2.0 window lists the libraries PowerBuilder will migrate.
4. Click OK.  PowerBuilder migrates the application libraries.  During the migration, PowerBuilder displays the status of the migration in the status bar.

When the migration is complete, the Migration window closes and the Library Painter workspace displays.

Recommendation

After you migrate your 1.0 applications to Version 2.0, you should:

Delete any background rectangles in your applications and replace them with the new window background attribute. To specify a window background color, select a color from the Window Color list in the drop-down list box in the Window Style window.

This is necessary because overlapping drawing objects paint differently in Version 2.0 than they did in 1.0, and background rectangles usually cause problems. 

If you changed the single quotation marks to double quotation marks in your embedded SQL, change them to single quotation marks.  PowerBuilder now handles single quotation marks properly.

Performance tips

Switch to Multiple Document Interface (MDI) wherever you simulate MDI in your 1.0 application.

Replace the Other event with one or more user-defined events or new PowerScript events (for example, Resize).