my suggestion would be a "meeting" table which would serve as the main table in the schema.
"meeting_attendees" would be a separate table with a one-to-many relationship between itself and "meeting". same with "takeaway". each takeaway item has its own unique ID (PK), and each relates to a specific meeting (meetingID from the meeting table as a FK). On 10/24/06, Daniel Kessler <[EMAIL PROTECTED]> wrote: > I have a form to collect meeting information. One type of > information is who attended, so we might have 8 attendies, as an > example. Usually in this case, I write 8 entries into the database. > All have the same form information but the attendies names are the > difference. Then when I query, I group them together (I believe). > > Thing is, I've never done a form where there was more than one field > that had this type of variance. Now, I have a "takeaways" field that > stores the path to a file. There can be several takeaways. I'm not > sure how to approach this. Do I insert a takeaway entry for each name > variance? IOW, say I have 8 names and 2 takeaways. Would I write 16 > entries just to cover the one form entry? > > Clearly I'm not advanced at DB work, so I would like a simple approach. > > thank you. > > > -- > > Daniel Kessler > > College of Health and Human Performance > University of Maryland > Suite 2387 Valley Drive > College Park, MD 20742-2611 > Phone: 301-405-2545 > http://hhp.umd.edu > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257898 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
