|
Required code change for Palm applications Your code must specify whether to use standard record-based database storage or to use the file-based expansion card storage for Palm Computing Platform version 4.x. You must add a single function call before calling ULPalmLaunch (embedded SQL) or ULData.PalmLaunch (C++ API). The function calls are as follows:
ULEnablePalmRecordDB( &sqlca );
or
ULEnableFileDB( & sqlca );
Supply ULEnablePalmRecordDB if you use record-based storage, and ULEnableFileDB for file-based storage. If the device does not support file-based storage, ULPalmLaunch sets SQLCODE -82.
The following environments and/or features are no longer supported by UltraLite:
DOS target platform DOS is no longer a supported platform.
Metrowerks CodeWarrior 5 development platform CodeWarrior 6 is now required for UltraLite development.
Palm 2.x no longer supported UltraLite no longer supports development for Palm OS 2.x devices such as the PalmPilot Professional. Version 3.0 or later is required.
ULPalmDBStream and ULConduitStream deprecated The new synchronization stream for HotSync or ScoutSync synchronization on the Palm Computing Platform means that the ULPalmDBStream and ULConduitStream functions are obsolete. They are still accepted, but have no effect.
UltraLite generator uses external Java virtual machine The UltraLite Analyzer now runs external to the database engine, and so can be used against reference databases even if they are not Java-enabled.
UltraLite JDBC package name changed The package name for the UltraLite JDBC functions has been changed from com.sybase.asa.ultralite.jdbc to ianywhere.ultralite.jdbc. This requires a change to the import statements used for UltraLite applications.
All changes must be committed before download synchronization Download-only synchronization is no longer an exception to the rule that all changes must be committed before synchronization.
You should also check Adaptive Server Anywhere behavior changes, as some may have an impact on your application.