The short answer, yes. The arguments for implementing referential integrity are numerous and it is a key aspect of any database development, whether using Microsoft Access or another type of Database Management System. Although using referential integrity can be frustrating in some cases, as it restricts your ability to enter foreign keys before a corresponding primary key exists in the related. This applies even if you plan on adding the same data to the primary key seconds later. However, the benefits brought by referential integrity far outweigh the slight inconveniences that can occur, and in the end a major problem caused by not having referential integrity is far worse than having to enter the data in a specific order.
By now, I’m sure some are asking what problems referential integrity prevents. Well without referential integrity, you can enter foreign keys that do not match the corresponding primary key in the related table, depending on the type of database this could cause a lot of problems such as mismatched customer data and mismatched transaction records. Obviously this type of mistake could cause a huge loss of money and time if the mistake is not found in time.
Luckily for developers using the MS Access Office program, referential integrity is quite easily turned on and is an important feature in Microsoft Access. Simply select the “Design” tab and then “Relationships”. From there click and drag the two fields you wish to connect, you will be prompted with the following dialogue box where you just need to check the “Enforce Referential Integrity” and hit “Create”.