Frequently Asked Questions

1c. preparing your client application

Q: what considerations must I allow for to ready my client application for a SyncSmart implementation?

A: in order to propagate record changes throughout any distributed database system, a methodology for creating system-wide unique identifiers must exist. If your database was changed to support system-wide unique identifiers for records, then you must modify your application so that the identifiers are generated properly.

If your client application database supports triggers (i.e. Microsoft database engine - MSDE), then there is no need to modify your application source code further. For client databases that do not support triggers (such as Microsoft access), your application must be modified to perform the synchronization-specific activities on SyncSmart columns and tables that are added to your client database at installation. There are three types of application operations that must be modified to support synchronization. They are insert operations, update operations, and delete operations. Data Safety Corporation provides the sample code necessary to integrate the operations logic into your application. (For detailed information on the application logic required to support a SyncSmart implementation, please refer to the SyncSmart integration guide.)