Table of contents
Collapse the table of content
Expand the table of content

Change Tables Involved in a One-to-Many Relationship in a DAO Recordset

office 365 dev account|Last Updated: 6/12/2017
1 Contributor

Dynaset-type Recordset objects can be based on a multiple-table query containing tables with a one-to-many relationship. For example, suppose you want to create a multiple-table query that combines fields from the Orders and Order Details tables. Generally speaking, you cannot change values in the Orders table because it is on the "one" side of the relationship. Depending on your application, however, you may want to be able to make changes to the Orders table.

To make it possible to freely change the values on the "one" side of a one-to-many relationship, use the dbInconsistent constant of the OpenRecordset method to create an inconsistent dynaset. For example.

Set rstTotalSales = dbs.OpenRecordset("Sales Totals" ,,dbInconsistent)

When you update an inconsistent dynaset, you can easily destroy the referential integrity of the data in the dynaset. You must take care to understand how the data is related across the one-to-many relationship and to update the values on both sides in a way that preserves data integrity. The dbInconsistent constant is available only for dynaset-type Recordset objects. It is ignored for table, snapshot, and forward-only-type Recordset objects, but no compile or run-time error is returned if the dbInconsistent constant is used with those types of Recordset objects. Even with an inconsistent Recordset, some fields may not be updatable. For example, you cannot change the value of an AutoNumber field, and a Recordset based on certain linked tables may not be updatable.

© 2018 Microsoft