Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / May 2005

Tip: Looking for answers? Try searching our database.

Cemetery Table Question

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jake - 27 May 2005 05:56 GMT
I still working on my funeral home program!?!
The first table (Vitals) is used on every case...the next table
(Cemetery) is used approx 50% of the time...they are ralated one to
one.

My question: what is the proper way to set up the relationship.
Enforce Referential Integrity  (yes or no)
Cascade Updated Related Fields (yes or no)
Cascase Delete Related Fields (yes or no)

Thank you Jake
John Vinson - 27 May 2005 06:17 GMT
>I still working on my funeral home program!?!
>The first table (Vitals) is used on every case...the next table
[quoted text clipped - 7 lines]
>
>Thank you Jake

It depends more on the nature of the data in the tables, and the
nature of the joining fields.

Enforce RI? Almost surely Yes. I don't know what the real-life logical
relationship between a record in Vitals and a record in Cemetary might
be, but I'd guess that you want to ensure that you don't make use of a
nonexistant Cemetary to bury a person (or, bury a person who never
existed). RI will prevent that.

Cascade Update? Depends on the nature of the joining field. This is
actually rather rarely useful: all it does is that if you *edit* -
change the value of - the "one" side table's linking field, that same
change will be made in all of the child table's records. If you are
linking from an Autonumber field you can't edit it anyhow so it makes
no sense to cascade updates that will never happen.

Cascade Deletes? Almost certainly not. Setting that will cause *every*
record in the Child table which matches a record in the Master table
to be automatically, irreversibly, and silently deleted whenever you
delete a main table record.

                 John W. Vinson[MVP]    
jake - 27 May 2005 06:21 GMT
Thanks John... I can't believe one minute I'm reading your book and the
next your typing a response to one of my questions...what a great world
we live in and thank you for your help.
Jake
Jeff Conrad - 27 May 2005 06:28 GMT
> Thanks John... I can't believe one minute I'm reading your book and the
> next your typing a response to one of my questions...what a great world
> we live in and thank you for your help.

John, have you written a book????
Or is Jake confusing you with John Viescas?

Signature

Jeff Conrad
Access Junkie
Bend, Oregon

jake - 27 May 2005 06:35 GMT
If he didn't write the book, he should have... he's very good! :)
John Vinson - 28 May 2005 02:06 GMT
>Thanks John... I can't believe one minute I'm reading your book and the
>next your typing a response to one of my questions...what a great world
>we live in and thank you for your help.
>Jake

I don't have the attention span to write books... my esteemed
colleague and friend John Viescas has written several, and they are
most of them on my bookshelves (or my desk, getting used and thumbed
up). Glad it worked for you, and thanks for the compliment!

                 John W. Vinson[MVP]    
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.