MobiLink Synchronization User's Guide
Synchronization Techniques
Adding synchronization functionality to an application adds an added level of complexity to your application. The following tips may be useful.
Wait If you try to add synchronization to a prototype application, it can be difficult to see which components are causing problems. This is particularly the case with UltraLite applications, where database and application are compiled together. When developing a prototype, temporarily hard code INSERT statements in your application to provide data for testing and demonstration purposes. Once your prototype is working correctly, enable synchronization and discard the temporary INSERT statements.
Go step-by-step Start with straightforward synchronization techniques. Operations such as a simple upload or download require only one or two scripts. Once those are working correctly, you can introduce more advanced techniques, such as timestamps, primary key pools, and conflict resolution.
Following are some fundamental rules of MobiLink synchronization applications.
Every table that is to be synchronized must have a primary key.
Don't update the values of primary keys.
Primary keys must be unique across all synchronized databases.
The MobiLink user ID that identifies each remote database must be unique.