Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data

Retrying the upload. Working around a known ODBC driver problem

Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering

MobiLink Synchronization Reference
MobiLink Synchronization Server Warning Messages
MobiLink synchronization server warning descriptions

Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data

Item	Value
Warning code	10016
Level	3
Parameter 1	Table name.

Probable cause

A remote database is synchronizing a table with at least one timestamp column while the timestamp precision of the remote database is lower than that of the consolidated database. The downloaded value will lose precision after being stored into the remote database.

This situation creates a virtual difference in the synchronized timestamp data between the consolidated database and the remote database. To avoid this data inconsistency problem, you should align timestamp precision across all databases involved in your synchronization system.