Migrate Application dialog box
Description
Migrates the selected application libraries to the current
version of PowerBuilder.
Migration also makes some modifications to your code so that
it continues to work as expected in Unicode. For example, if it
is not already present, the clause Alias For is
appended to the definition of external functions that have an argument
or return a value whose datatype is string, char, or structure,
and the string ;ansi is appended to the name
of the function in the Alias For clause. PowerBuilder
records the changes it makes and other recommended changes in a
log file.
Dialog options
-
Browse
Click to search for additional libraries that you want to
migrate. You can select and delete libraries from the list of those
to be migrated. Libraries that are not in the application search
path will not appear in the list of libraries to be migrated.You can open the Application painter and select an application
with a search path that contains the libraries you want to migrate
or modify the library search path of the current application. -
Convert DBCS String-Manipulation Functions
This check box is provided so that users in double-byte character
set (DBCS) environments can choose to have string-manipulation functions modified
automatically.In PowerBuilder 9 and earlier, string-manipulation functions
such as Len, Mid, and Pos returned
the number of bytes in a string or used a number of bytes as an
argument. In this version, string-manipulation functions return a
number of characters or take a number of characters as an argument.If you work in a single-byte character set (SBCS) environment,
you do not need to modify any of these functions when you migrate
from PowerBuilder 9 or earlier. They produce the same results as
in PowerBuilder 9 and earlier because PowerBuilder now uses Unicode encoding
internally. Do not select this check box in an SBCS environment.If you work in a DBCS environment, you must replace all occurrences
of each of these functions with the equivalent function with an A suffix
when you migrate from PowerBuilder 9 or earlier. For example, you
must replace Len with LenA.In PowerBuilder 9 and earlier, functions with a W suffix
were used to manipulate characters instead of bytes in DBCS environments.
Functions with and without the W suffix both
manipulate characters in this version of PowerBuilder. The functions
with the W suffix are provided for backward compatibility
and are considered obsolete, therefore it is recommended that you
replace them. For example, you should replace LenW with Len. -
Messages
If any errors or warnings messages are generated, they are
displayed. You can choose to display informational and obsolete
messages. -
Information
Check if you want to see informational messages about the
migration. You can save this information to a file or send it directly
to a printer. -
Obsolete
Check if you want to see messages about obsolete code in your application. Obsolete
code uses constructs that will not be available in a future release
of PowerBuilder.