About this book

Audience

This guide is for programmers building applications with PocketBuilder™.

This guide assumes that you have a basic familiarity with Windows CE (Windows Mobile) devices. Although your development work in PocketBuilder is done on a desktop machine, you design applications for use on Windows CE devices such as the Pocket PC or Smartphone.

For information about developing applications for Microsoft Windows CE platforms, see the Microsoft Web site. You can also find helpful information at the Pocket PC Developer Network Web site.

How to use this book

PocketBuilder is very similar to PowerBuilder®, the Sybase® 4GL development tool for desktop applications and application server components.

If you have never used PowerBuilder, use this book to learn some concepts and principles of programming in PowerScript®, the language used in both PowerBuilder and PocketBuilder, as well as programming techniques you can use with controls in windows and DataWindow® objects. This book also describes how to manage database connections and provides a reference to database connection parameters and preferences.

If you are a PowerBuilder user, the following chapters are probably the most useful:

Related documents

PocketBuilder documentation The PocketBuilder documentation set also includes the following manuals:

PocketBuilder reference set The PocketBuilder reference set is made up of four manuals that are based on PowerBuilder documentation:

Online Help Reference information for PowerScript properties, events, and functions is available in the online Help with annotations indicating which objects and methods are applicable to PocketBuilder.

SQL Anywhere® Studio documentation PocketBuilder is tightly integrated with SQL Anywhere (formerly Adaptive Server Anywhere), UltraLite®, and MobiLink, which are components of SQL Anywhere Studio. You can install these products from the PocketBuilder setup program. For an introduction to these products, see Chapter 1 in the Introduction to PocketBuilder.

Sample applications

The PocketBuilder installation provides a Code Examples workspace with targets that illustrate many of the product's features. Commented text inside events of target objects helps explain the purpose of the sample code. The example workspace is installed in the Code Examples subdirectory under the main PocketBuilder directory.

More applications on the Web

You can find more sample PocketBuilder applications and techniques in the PocketBuilder project on the Sybase CodeXchange Web site. There is a link to this page on the Windows Start menu at Program Files>Sybase>PocketBuilder 2.0>Code Samples.

If you have not logged in to MySybase, you must log in to the Sybase Universal Login page to access CodeXchange. If you do not have a MySybase account, you can sign up. MySybase is a free service that provides a personalized portal into the Sybase Web site.

Other sources of information

Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:

Sybase EBFs and software maintenance

StepsFinding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.

Conventions

The formatting conventions used in this manual are:

Formatting example

To indicate

Retrieve and Update

When used in descriptive text, this font indicates:

  • Command and function names

  • Keywords such as true, false, and null

  • Datatypes such as integer and char

  • Database column names such as emp_id and f_name

  • User-defined objects such as dw_emp or w_main

variable or file name

When used in descriptive text and syntax descriptions, oblique font indicates:

  • Variables, such as myCounter

  • Parts of input for which you must substitute text, such as pklname.pkd

  • File and path names

File>Save

Menu names and menu items are displayed in plain text. The greater than symbol (>) shows you how to navigate menu selections. For example, File>Save indicates “select Save from the File menu.”

dw_1.Update()

Monospace font indicates:

  • Information that you enter in a dialog box or on a command line

  • Sample script fragments

  • Sample output fragments

If you need help

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.