I think I would approach it like so; Create three tables called tbl_Artist, tbl_CD, tbl_Track.
tbl_Artist Artist_ID Artist_Name Artist_Genre, etc.... tbl_CD CD_ID Artist_ID CD_Title CD_Price, etc... tbl_Track Track_ID CD_ID Track_Name Track_Price (assuming you are selling tracks, thus allowin the consumer to create custom CD's) Anyway, now you have a relationship between the three tables. I am sure tha t you will have other replies, and I am sure that they may be better than t his as I am not a DBA. Also, there is a discussion group called CF_SQL that you might want to post this to. Bruce ---------- Original Message ---------------------------------- From: "Douglas Brown" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Tue, 15 Jan 2002 14:00:32 -0800 I am trying to figure out how I should set up a database for an ecommerce site. I will be selling music CD's. Each artist can have several albums, and each album can have several tracks. I am pretty sure I will need 3 tables for that info. What I am wondering , is where should I keep pricing info and such? Should it be in the album table or should there be a seperate table for pricing etc. Any insight would be helpful There are two major products that come out of Berkeley: LSD and [Unix] BSD. We don't believe this to be a coincidence. Doug Brown ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
