I'm a big fan of tables. The more the better, there is no reason why all that should live in the same table. I also like auto incremnt on tables so every table can have a ID, tblClient.clientID, tblClientBroker.BrokerID, tblClientStats.StatID
It's just cleaner looking and allows you to do way more with the data as people start asking for new features. The stats and broker tables need a ClientID field to link them back together. Casey Dougall Web Applications Developer Ph: 518 743-9424 Fax: 743-0337 Mannix Marketing Inc. 33 Park St. Third Floor, Glens Falls, New York 12801 Marketing to New York State Destinations? We offer quality Travel Industry Directories, Including www.Albany.com, www.LakeGeorge.com & www.Saratoga.com > > > >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:247565 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
