Home > Articles > Home & Office Computing

This chapter is from the book

The field that joins two tables on the one side of a one-to-many relationship must be a primary key field or must have a unique index so that the Jet Engine can maintain referential integrity. If the index on the one side of the relationship is not unique, there is no way to determine to which parent a child record belongs.

In Access 2003, it is not necessary to create an index for the field on the many side of the relationship. Access 2003 will create an internal index for you. If you do create an index on the many side of the relationship, make sure that you set the index to Yes (Duplicates OK); otherwise, you will have a one-to-one, rather than a one-to-many, relationship.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.