UltraLite Database User's Guide
Synchronization for UltraLite Applications
Designing synchronization for your UltraLite database
Some applications include tables in the UltraLite database that are not updated locally. Price lists and company policies are two examples. You can synchronize these tables efficiently by including them in a publication, and synchronizing the publication using download-only synchronization. Download-only synchronization is less time-consuming than a two-way synchronization, as no data is uploaded.
To use download-only synchronization, you must ensure that the data is not changed locally. If any data is changed locally, synchronization fails with a SQLE_DOWNLOAD_CONFLICT error.
Unlike for two-way synchronization, you do not have to commit all changes to the UltraLite database before download-only synchronization. Uncommitted changes to tables not involved in synchronization are not uploaded, and so there incomplete transactions do not cause problems.
For information on download-only synchronization, see the following:
MobileVB See SyncParms.
ActiveX See SyncParms.
Native UltraLite for Java See ianywhere.native_ultralite.SyncParms in the API Reference.
Embedded SQL See download_only synchronization parameter.
Static C++ API See download_only synchronization parameter.
Static Java API See download_only synchronization parameter.