Hi Hendra,
Relationships are a different issue than having indexed fields on the many
side. In my opinion, the most important aspect of building relationship is
the possibility of enforcing referential integrity. Without referential
integrity, it is possible, even probable, that orphaned records will get
created in the many table. So you could, for example, have Invoices without
customers, and invoice details without invoices. Orphaned records are
absolutely undesirable. So yes you still should have relationships
established.
Glenn
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
agesthahendra@ymail.com
Sent: February-27-12 10:30 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Relationships
Hi All,..
Assumed :
- We have indexed all of the foreign key on many sides
- All Join are builded in Queries as we need
- Ignoring Enforce Reffrential Integrity
Do we still have to build relationships between tables..? What about
performance..? Are there any performance effects if we don't build
relationships between tables..?
Any explanation would be appreciated, thank you...
Regards
Hendra
[Non-text portions of this message have been removed]
Senin, 27 Februari 2012
RE: [MS_AccessPros] Relationships
__._,_.___
.
__,_._,___
Langganan:
Posting Komentar (Atom)
Tidak ada komentar:
Posting Komentar