Re: Relational Design

I like the idea of enforcing a unique address at the time data entry,

Would it be better to divide up the address components into columns and use the combination as a unique key? Or is there a performance hit on the database with this method?

G Bramfield <lgbram_at_telusplanet.net> wrote in message news:4Mxb5.33161$FQ.3485646_at_news0.telusplanet.net...
> Hi Flash! You want to set up a one-to-many relationship between address
 and
> volunteer. This means that one address can be assigned to several
 different
> people(volunteers). It sounds like you really only need one table to
> accomplish your task.
> To pull all of the data related to a specific address all you need to do
 is
> pass the address value to a query. You can do this by creating a
 parameter
> query, or you can reference a value entered into a form by the user.
>
> If you were going to create a parameter query, simply type the following
> code into the criteria of the "address" field: [Enter Address]. Or, if
 you
> wanted to reference a value from within a form, you wold type the
 following
> piece of code in the same place: Forms!frmMyForm!ctlMyControl.
>
> This should be enough to get you started. Good luck!
>
> Regards, G!
> Flash <nospam_at_nospam.com> wrote in message
> news:PEnb5.15181$7%3.961830_at_news.flash.net...
> > I am going to be creating a database that tracks volunteers. To cut
 down
 on
> > duplicate mailings I'm looking for a design that would enforce a one to
 many
> > relationship with a unique address allow multiple names.
> >
> > This way, when data was being entered and the user chooses an address
 all
> > the names associated with that address appear.
> >
> > How should I model this database?
> >
> >
>
>
Received on Fri Jul 14 2000 - 00:00:00 CEST