FIX: Clearing "Enforce constraint for replication" Check Box for a CHECK Constraint Breaks Constraint Checking on All Nonreplication Operations

This article was previously published under Q278021
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57939 (SQLBUG_70)
This problem only occurs when using SQL Server 2000 Enterprise Manager against a SQL Server 7.0 server. When you design a table, if you clear the Enforce constraint for replication check box for any specified constraint, constraint checking no longer applies on any user operation, not just replication. (This setting should not affect user edit mode, but only the replication process.) After you add a value outside of the range specified by the constraint, you will not be able to change that value again (whether valid or not), and you will receive the following error message:
Another user has modified the contents or tables of this view; the database row you modified no longer exists in the database.
Database Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot perform direct UPDATE to range maintained by replication. This conflict occurred in database 'pubs', table 'jobs', column 'max_lvl'.
This statement has been terminated.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
constraint "enterprise manager" replication

Article ID: 278021 - Last Review: 10/26/2013 05:22:00 - Revision: 3.0

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB278021