FIX: Conflict Viewer Shows Incorrect Format for Datetime Column

Article translations Article translations
Article ID: 240194 - View products that this article applies to.
This article was previously published under Q240194
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56339 (SQLBUG_70)
Expand all | Collapse all

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 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

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.

Properties

Article ID: 240194 - Last Review: October 22, 2013 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB240194

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com