[AccessD] Invitations DB Design Ideas

Will there only be two persons' names at most?  If not, then you can put the 
names in a name table with a foreign key to the Invitation table's primary 
key.

Source could also be a table with a FK in the Invitation pointing to the 
source table's PK.

Seems like maybe more trouble than it's worth for this app, though.

Rocky

----- Original Message ----- 
From: "Joe Hecht" <jmhecht at earthlink.net>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, June 01, 2005 9:37 PM
Subject: [AccessD] Invitations DB Design Ideas


> So my niece got engaged and I figure I better get my DB going soon.
>
> Right now the database is one table,
>
> These are typed in to readable and not names with spaces etc:
>
> I rec num
> 1st Person first Name
> 1st person last name
> 2cd person first name
> 2cd person last name
> Address fields
> Adults Invitation Represents
> Children Invitation represents
> Contact phone
> Memo
> Source (Bride/Groom/Family/friend?)
> Invited Y/N
> Coming y/n
> Gift received Y/N
> Note Sent Y/N
>
>
>
> Looking for ideas to normalize this
>
> OK wise guys, I know no wedding is normal but...
>
>
>
> Joe Hecht
> Los Angeles CA
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>