Article ID: 278390 - View products that this article applies to.
This article was previously published under Q278390
This article has been archived. It is offered "as is" and will no longer be updated.
A Microsoft Access database that is generated from a Visio database model does not propagate the referential integrity rules for cascading updates and deletes.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Manually enable the cascade update or delete (or both) through Microsoft Access after the new database is created. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Article ID: 278390 - Last Review: October 21, 2013 - Revision: 1.6