What's New in SQL Anywhere Studio
  Upgrading Software and Databases

Upgrading UltraLite applications

To upgrade to version 9, you must rebuild your UltraLite application with version 9 software. This includes running the version 9 UltraLite generator and linking against the version 9 libraries.

To run the version 9 UltraLite generator, either explicitly include the path in your command line, or ensure that the version 9 directory appears ahead of older version directories in your system path.

To take advantage of added Palm code segmentation you must upgrade your reference database. Otherwise, all Palm code will go in the same segment. If you are developing for platforms other than the Palm Computing Platform, you do not need to upgrade your reference database to version 9 to generate a version 9 application.

Palm development 

When working with version 8 or version  9 software, you must add a function call before calling ULPalmLaunch (embedded SQL) or ULData.PalmLaunch (C++ API), to indicate the storage type to use. The function calls are as follows:

ULEnablePalmRecordDB( &sqlca );

or

ULEnableFileDB( &sqlca );

Call ULEnablePalmRecordDB to use primary record-based storage, and ULEnableFileDB for secondary file-based storage. If the device does not support file-based storage, ULPalmLaunch sets SQLCODE -82.

Upgrading deployed databases 

Before upgrading a deployed UltraLite database, you should ensure all changes are synchronized. For Palm applications, it is recommended that you use a new Creator ID for each version of your application, install a new application, and delete the old application and database from the Palm device. If you use the same Creator ID, you should delete the existing application first.

The UltraLite software can upgrade databases subject to some conditions. For more information, see Altering the schema of UltraLite databases, and Upgrading UltraLite software.

UltraLite version 9 applications require a MobiLink version 9 synchronization server for synchronization. UltraLite version 9 applications do not synchronize with a MobiLink synchronization server older than version 9. For information on upgrading MobiLink, see Upgrading MobiLink.

When deploying a new version of a MobiLink application, it is recommended that you use a new version name for the synchronization scripts. This makes it easier to upgrade the remote databases incrementally, rather than all at once.