Forum home » Delegate support and help forum » Microsoft Access Training and help » access advanced courses - Referential integrity
|
|
|
The UK's most regular Training information: See also: |
|
Welcome. Please choose your application (eg. Excel) and then post your question. Our Microsoft Qualified trainers will then respond within 24 hours (working days). Frequently Asked Questions
Any suggestions, questions or comments? Please post in the Improve the forum thread. |
access advanced courses - Referential integrity
Resolved · Low Priority · Version Standard
Reply Tue 5 Jun 2007, 13:45Delegate Tim said...
Tim has attended:
Access Intermediate course
Access Advanced course
Referential integrity
Is it advisable when setting up relationships to enforce referential integrity as a default and then remove only when and if required?
For upcoming training course dates see: Pricing & availability
RE: Referential integrity
Hi Tim,
Referential integrity is very powerful when used in the correct context. I would not suggest using referential integrity as a default, unless you are very clear about what you are wanting to enforce. Not all tables need or require it, so I would suggest leaving it off, until you know you need it. This should ideally be built into your database plan, so that you are aware of its requirement prior to building the database.
ie - if you know that you want to ensure that a client number exists, prior to creating an order, then enfore referential integrity.
If you are in the design phase of the database, you might find it frustrating to enable all the referential integrity, only to find that it hinders your development progress.
Regards
Richard
|