Hi, we are having some trouble with our merge replication between a SQL
Server 2005 and a SQL Mobile for Windows Mobile 5.
Our replication is a simple one with vertical partition set to true, and
column tracking set to true. We have no conflict detection/resolution for
logical rows. We have added a few columns for replication via
sp_mergearticlecolumn but not all columns available in table.
If we create a new post on the mobile SQL and synchronize it with the
server, everything works as intended with a new row being created at the
server. However if we update the very same row at the mobile after that and
synchronize again, only some of the published columns will actually be
replicated to the server. The rest will not be updated in any way - thus
after a synchronization, the row on the server and the row on the handheld
still differ.
Here are some other facts:
* We have no triggers, constraints or any other kind of logic that could
interfere with the synchronization.
* Only datetime fields and varchar fields seem to be affected. The rest will
sync as normal.
* Some datetime fields does work however, so it might be a red herring.
* If we sync with a swedish mobile 5.0 the dates will synchronize correctly
but varchar fields will still not update. If we sync with a US mobile 5.0
neither dates nor varchar fields will update during sync.
* If we change column_tracking to false everything will work as intended.
However we require column_tracking for our application so we can't back on
this.
Since we get different results depending on OS nationality and only
datetimes and varchars are affected we are thinking the bug is somehow
related to a collation difference between the databases or something similar.
The strange thing though is that we are using a SQLCeReplication object to
create our database for us. Thus one could hope that we would be given a db
that matches the subscription it is created for.
Any help is very appreciated.
