Relational Databases: Enforce Referential Integrity?

[Mod]

I'm building a database with 23 tables (so far) and about 30 foreign keys, spread out amongst the tables.

So far I haven't concerned my self with the "Enforce Referential Integrity" option in the database, I figure if the interface (read as: forms) is(are) designed right, the integrity of the data shouldn't be an issue.

It's almost time to go live with the project though, and I'm having second thoughts. My concern is that I'm not sure exactly what the behaviour of the database will be if all relationships have this option checked.

Is it normally considered a useful feature? Are there any reasons to avoid letting Access 'Enforce Referential Integrity'?

What, in general, is everybody's opinion of this feature?

 

[The_Doc_Man]

Look in this forum for a post originated yesterday (Tuesday) by Philljp390, on the same topic. Several persons posted there in response to a nearly identical question.

 

[Kevin_S]

Mod -

General Database Design practices dictate that you should always enforce business rules at the lowest possible level. The lowest possible level is that of data service i.e. tables and their relationships. This is a common practice and should not be ignored... Follow the Doc's advice and continue reading on the subject for more info...

HTH,
Kev

 

[KenHigg]

It's almost time to go live with the project though

If you have run the db through the acid test all the way, and an issue has not come up where RI is needed, then you should be good to go. But, I can't for the life of me imagine a db with 23 tables that would not require RI...

???
ken

 

[Mod]

oops sorry, i really should have checked for other threads.

 

[Pat Hartman]

I have had occassion to work with numerous databases (not just Access) that were developed by people who didn't know enough (or thought they knew better) to enforce referential integrity. In all cases, one or more tables in the database contained invalid data that would have been prevented by simply setting RI to be enforced by the database engine.