Thread: Church Database
View Single Post
  #19  
Old March 3rd, 2010, 10:55 PM posted to microsoft.public.access.tablesdbdesign
Kathy R.[_3_]
external usenet poster
 
Posts: 25
Default Church Database

Fred wrote:
The one thing I question structurally in your description is a subform for
addresses. This also implies a separate table. IMHO addresses are "one to
one" information for one of the other tables, and thus should probably be in
the table and form with that other entity.



Hi Fred,

Normally I would agree with you about the addresses. I do, indeed, have
a separate table for addresses. Within our congregation we have close
to a dozen families that head south for the winter (2-3 months at a
time) to permanent addresses there. I have to change their addresses
each winter and spring. In addition, we have another half dozen or more
college students. They have both home and college addresses and would
also need to be changed twice a year. Plus, the church is in a college
town and we have students from the college that attend that we keep
track of - again a home and college address.

For this reason I've put the addresses in a separate table. This way I
can just check which is active instead of changing the address back and
forth each year. I debated with myself about this and finally decided
that, once I have the tables/forms/reports setup, it would be easier to
just check a yes/no box than change the address each time.

Thank you for your comments. I really appreciate them!

Kathy R.
PS I won the debate, by the way. ;-)