Timestamp Causing Mobilink Sync Fail

[Zoe]

I have an ASA 9.0.2 consolidated database syncing with a remote
reporting database.
The download_cursor sync script is 'Select col1, col2, col3 from table
where last_modified >=?'
The last_modified field on the cons is a timestamp - current utc
timestamp.

The table causing the issue will almost always have the same amount of
rows in it with the primary keys staying the same and 3 colums on each
row are updated constantly.

When I updated this table through TSQL, the last_modified date was not
being updated therefore the modified data was not being downloaded to
the remote reporting database.

I changed the update TSQL procedure to set the last_modified = current
utc timestamp however this causes the sync to fail.

I found out that by setting the last_modified field to 'utc timestamp'
will force a row to update the timestamp when an update occurs.
However this still causes the sync to fail.

I have eliminated any other reasons for the sync to fail.

Should I be using a different sync stript for the updates? and just
use the download_cursor script for inserts? Is there a known issue
with timestamp??

Any Ideas Suggestions?

[Zoe]

Removing the table from its current publication and placing it in a
separate publication on its own has stopped the sync from failing..
any suggestions as to why this was happening??