BUG: Conflict Viewer Shows Incorrect Format for Datetime Column

• Microsoft SQL Server version 7.0

SYMPTOMS

When the datetime column is updated in tables involved in merge replication such that this results in a conflict, the datetime column is displayed in mm/dd/yyyy format in the conflict viewer and the time portion of the datetime column is not displayed. This may result in time data loss when changing date data on the conflict viewer wizard.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

If the merge conflict in the datetime column is resolved choosing keep revised data or the overwrite with revised data option by modifying just the date portion of the datetime column, the time portion of the datetime column is overwritten with 00:00:00.000 even though it may have had a non zero value before resolving/overwriting with revised data. Therefore, any time information that existed before the conflict resolution may be discarded.

Additional query words:

Keywords :
Version : winnt:7.0
Platform : winnt
Issue type : kbbug