You can create only Single Document Interface (SDI) applications for Windows CE. Although you can import a PowerBuilder application target into PocketBuilder, you must remove Multiple Document Interface (MDI) windows from a PowerBuilder application before you import it to PocketBuilder for use on Windows CE devices.
For information on importing PowerBuilder targets, see “Import Desktop to Pocket” and “Converting a PowerBuilder application”.
The Target page of the New dialog box in PocketBuilder has wizards that you can use to create or convert PowerScript targets and to add the targets to a PocketBuilder workspace:
The Application Target wizard creates an Application object and the library (PKL) and target (PKT) containing it.
The PocketPC and SmartPhone Application Creation Target wizards create an Application object, a PKL, and a PKT, as well as a set of basic objects and scripts. If the application requires a connection to a SQL database, the wizard automatically creates a connection object and integrates it into the application.
The Existing Application Target wizard adds a target to your workspace that uses an existing application. In the wizard, you must select an Application object in a PKL file.
After you complete the wizard, the Migrate Application dialog box opens if you need to migrate the application for compatibility to the current PocketBuilder version.
Before you migrate
Always make a backup copy of all the PKL files used in an
application before you migrate it or convert it to the current version
of PocketBuilder.
You should check the PocketBuilder Release Bulletin for the version you are using to find out if there are migration issues that might affect you.
You can select a PowerScript target that was built in PowerBuilder 7, 8, 9, or 10 and convert it to a PocketBuilder target. The Import Desktop to Pocket wizard copies and converts into PKL files all the PBL files in the target you select on the first page of the wizard. The wizard also references the PKL files in a new target with a PKT extension.
The original target and libraries are left in their original directories, which is also where the new target and migrated libraries are saved. The conversion wizard gives you the option of adding the new target to the current PocketBuilder workspace.
Files converted by the wizard keep the same names as the original files except for their extensions. The PowerBuilder VM for your source files (PBT and PBL files) must be in your system's PATH variable. The wizard uses the PBVMxx.DLL and the compiler PBCMPxx.DLL to convert the source files, where xx is the version of the PowerBuilder VM.
Generating an application that is not in the current workspace can cause compile errors during the conversion of PBL files to PKL files. However, once the target has been added to a workspace, a full rebuild fixes everything unless there are true compile errors in the library you are converting.
For additional considerations in converting a PowerBuilder application to a PocketBuilder application, see “Converting a PowerBuilder application”.
A wizard is available on the Tool page of the New dialog box for converting PocketBuilder targets to PowerBuilder targets. For information, see “Converting a PocketBuilder target to PowerBuilder”.
