Assuming I understand correctly, you have two
entities...audience and event. Each event on your
calendar can be classified under one to many audience
(types). Each audience (type) can be a classification
for zero to many events. That gives you a many to many
relationship between audience and event.

In order to normalize this, you need an intersection
table. I would create these three tables:

audience - audience_id (PK), audiencename
event - event_id (PK), eventname, eventdescription
audience_event - audevent_id (PK), audience_id (FK),
event_id (FK)


--- Kurt Wiersma <[EMAIL PROTECTED]> wrote:
> 
> I have a database which is going to hold events for
> a calendar app. In it I
> have a table for audiences which has an audienceID
> and audience name. Inside
> the calendar table I have a field for audienceIDs
> where I was thinking of
> keeping a comma delimited list of audienceIDs.
> 
> The problem is I cannot join the two tables very
> easily in this format. I
> want the user to be able to check a checkbox for
> each audience they would
> like the event to be categorized under.
> 
> Can anyone suggest a better database structure or
> code that would allow the
> two tables to be joined under this structure? Please
> cc my email address in
> the reply as I am on the digest format right now!
> 
> Thanks for you help,
> 
> -- Kurt
> 
>
------------------------------------------------------------------------------
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
>
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
> or send a message to
> [EMAIL PROTECTED] with 'unsubscribe'
> in the body.


__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to