Heck yeah... For sure split out the broker info. The stats could stay in there depending on what sort of data it is and how often it's updated.
<!----------------//------ andy matthews web developer certified advanced coldfusion programmer ICGLink, Inc. [EMAIL PROTECTED] 615.370.1530 x737 --------------//---------> -----Original Message----- From: Mike | NZSolutions Ltd [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 4:00 PM To: CF-Talk Subject: Database design Hi guys, I am creating a site for a property developer. Each time a client/potential client registers on the site the following info is stored in a table (simplified)... tblClient -------------- Client_id Client_fname Client_lname Client_address Client_city Client_ etc... -------------- Broker_name Broker_address Broker_city Broker_ etc... -------------- Stat_age_range Stat_price_range Stat_referral_type Question: is it worth my while to break this single table into multiple tables linked by client_id Eg. tblClient, tblClientBroker, tblClientStats Regards mike ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:247559 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
