Article ID: 201310 - View products that this article applies to.
This article was previously published under Q201310
This article has been archived. It is offered "as is" and will no longer be updated.
Advanced: Requires expert coding, interoperability, and multiuser skills.
When you upsize a Microsoft Access database that has constraints, the constraints are not upsized.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Steps to Reproduce ProblemThe following steps involve creating a new database containing a table with a CHECK constraint, upsizing it to SQL Server, creating a new Microsoft Access project in which to view the SQL Server database, and then, running a stored procedure that reveals that the constraint is not upsized:
For additional information about creating constraints in a Jet database, please see the following article in the Microsoft Knowledge Base:
201888For additional information about using SQL DDL to create and drop tables and relationships, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/201888/EN-US/ )ACC2000: How to Create a Jet CHECK Constraint
(http://support.microsoft.com/kb/209037/EN-US/ )ACC2000: Create and Drop Tables and Relationships Using SQL DDL
Contact us for more help