98.7% Of all customers recommend us, we're so confident about our results we publish all reviews and stats
View Live Stats View Reviews
Forum home » Delegate support and help forum » Microsoft Access Training and help » advanced microsoft access training courses in london - Referential Integrity
advanced microsoft access training courses in london - Referential Integrity
Resolved · Low Priority · Version Standard
Fri 16 Mar 2007, 16:54Delegate Brian said...
Brian has attended:
Access Intermediate course
Access Advanced course
Referential Integrity
Should you always enforce referential integrity when setting up relationships between tables? What would be an example if you didn't?
Tue 20 Mar 2007, 10:15Trainer Richard said...
RE: Referential Integrity
Hi Brian.
No, you should not ALWAYS enforce referntial integrity between relationships.
Using ORDERS and CUSTOMERS tables for example:
Generally it is a good idea to enforce it one way - IE. Customer record must exist for order to be created.
You might choose not to enforce the other way - IE. If Iyou delete a customer, there is no need to delete all the orders relating to it (for record keeping), or if you delete an order, you do not want the customer to be deleted too.
Does that clarify it for you?
Richard
Training information:
- Advanced microsoft access training courses in london
- Access course microsoft training
- Microsoft Access Training
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 tip:Using the Quick Access Toolbar in Access 2010The Quick Access Toolbar is included in virtually every Office product, including Outlook 2010, Word 2010, Excel 2010, and PowerPoint 2010. |
