CdbRelation Object

See Also   Methods   Properties

A CdbRelation object represents a relationship between fields in tables or queries (Microsoft Jet databases only).

Remarks

You can use the CdbRelation object to create new relationships and examine existing relationships in your database.

Using a CdbRelation object and its properties, you can:

• Specify an enforced relationship between fields in base tables (but not a relationship that involves a query or a linked table).
  
  
• Establish unenforced relationships between any type of table or query — native or linked.
  
  
• Use the Name property to refer to the relationship between the fields in the referenced primary table and the referencing foreign table.
  
  
• Use the Attributes property to determine whether the relationship between fields in the table is one-to-one or one-to-many and how to enforce referential integrity.
  
  
• Use the Attributes property to determine whether the Microsoft Jet database engine can perform cascading update and cascading delete operations on primary and foreign tables.
  
  
• Use the Attributes property to determine whether the relationship between fields in the table is left join or right join.
  
  
• Use the Name property of all CdbField objects in the Fields collection of a CdbRelation object to set or return the names of the fields in the primary key of the referenced table, or the ForeignName property settings of the CdbField objects to set or return the names of the fields in the foreign key of the referencing table.

If you make changes that violate the relationships established for the database, a trappable error occurs. If you request cascading update or cascading delete operations, the Microsoft Jet database engine also modifies the primary or foreign key tables to enforce the relationships you establish.

For example, the Northwind database contains a relationship between an Orders table and a Customers table. The CustomerID field of the Customers table is the primary key, and the CustomerID field of the Orders table is the foreign key. For Microsoft Jet to accept a new record in the Orders table, it searches the Customers table for a match on the CustomerID field of the Orders table. If Microsoft Jet doesn't find a match, it doesn't accept the new record and a trappable error occurs.

When you enforce referential integrity, a unique index must already exist for the key field of the referenced table. The Microsoft Jet database engine automatically creates an index with the Foreign property set to act as the foreign key in the referencing table.

To create a new CdbRelation object, use the CreateRelation method. To refer to a CdbRelation object in a collection by its ordinal number or by its Name property setting, use either of the following syntax forms:

Relations[0]

Relations["name"]

CdbRelation Constructor Syntax

Use any one of the following three constructors. The qualifier 'CONSTRUCTOR' in the syntax models is provided to help readability. It has no syntactic value.

CONSTRUCTORCdbRelation(VOID);

This constructor creates an instance of the class. There are no parameters.

CONSTRUCTORCdbRelation(const CdbRelation &);

This constructor creates a copy of the object referenced in the parameter.

CONSTRUCTORCdbRelation(DAORelation *prl,

BOOL bAddRef = FALSE);

DAO functionality is presented through pointers to DAO Automation interfaces. This constructor makes a DAO interface available in the form of a DAO class object that provides additional functionality.

This constructor is not required for typical use. It is provided to enable you to easily create a DAO class object if you have access to the corresponding DAO interface.

When the destructor for the DAO object is invoked, the underlying Automation interface's Release member is called. If Release decrements the interface's reference count to zero, the pointer to the Automation interface can be deleted. If you don't want this to happen (for example, because you want to discard the DAO object, but continue using the Automation interface), specify TRUE for the second parameter. The underlying Automation interface's AddRef member is called, which counterbalances the eventual call to Release.