No help whatsoever but for future reference: This arrangement is sometimes referred to as a "Vertical Partition" as opposed to "Horizontal Partitions" which is what you might use for archiving data etc.
Vertical Partitions are definitely worth considering for saving space if the circumstances are as you describe. The most convenient way to deal with them is to create a database view - preferably and updatable view that joins the two tables. Then you just perform the single insert/update on the view as normal. Andr� -----Original Message----- From: Rick Kennerly [mailto:[EMAIL PROTECTED] Sent: 02 September 2003 13:54 To: CF-Talk Subject: Mutiple SQL Inserts I didn't realize until this project that all of my relational database work was kind of one-dimensional, all of the related tables were built with dropdowns to feed the main table in mind. None of the related tables update information by users. Now I have a project where I need to add several fields to a well-established table in a db. However, only one in 500 new inserts would need these fields, so a related (sub)table is the way to go to save space. The problem is, not one of my references addresses an example of multiple Inserts into a DB. I've thought of two approaches. Is there a best practice? (or something I haven't thought of?) Action_Form Query>insert info into new related table Query>get row number from new related table Query>pass the row number of the new related table to the form and Insert the entire form into main table all in one shot or a series of forms and action pages that kind of step through the transaction. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 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
