Ack. Always keep one-to-many stuff relational on general principles. Its not that much extra work.
--------------------------------------- Matt Robertson, MSB Designs, Inc. http://mysecretbase.com - Retail http://foohbar.org - ColdFusion Tools --------------------------------------- ---------- Original Message ---------------------------------- from: Janine Jakim <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Thu, 21 Nov 2002 15:59:20 -0500 >hmmm- I am very into keepting my database relational, but am wondering what >the best route for thi particular issue is... >Heres' the scoop >1. One student can be working on many goals so I have 1 one to many >relationships. >2. Each goal needs graded every marking period (up to 6 times a year)- >these are not traditioanl grades but a long comments piece) So goals have a >one to many relationship with the grades. >I'm thinking the best way to handle it is to break it into 3 tables >table one student info >table 2 all the goals for the students hooked to students with the studentid >table 3 all the grades for the goals hooked to goals by goalID > >My other option is to have 2 tables >table one student info >table two goals + 6 grading periods comment sections >Thanks in advance for any input. >j > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
