Relational Design
From: Flash <nospam_at_nospam.com>
Date: 2000/07/13
Message-ID: <PEnb5.15181$7%3.961830_at_news.flash.net>#1/1
Date: 2000/07/13
Message-ID: <PEnb5.15181$7%3.961830_at_news.flash.net>#1/1
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 Thu Jul 13 2000 - 00:00:00 CEST