> Brian Henning wrote: > > > Howdy Folks, > > Just wondering what people's opinions are on the following topic: > > a) One table with copious fields > > -vs- > > b) Multiple tables with fewer fields each, linked somehow
Scott said: > If a single column of the table will be used as the search > field, e.g. > customer number, a single table is not such a bad idea. The > column can > be used as the index, and access will remain fairly efficient. > > If two or more columns will be used this way, it's a better > idea to look > for a logical way to divide the table so that the two tables can be > indexed individually if possible. > It is for this specific reason that I prefer multiple tables. I like to at least have the option of indexing different sets of data. MPF ----- Confidentiality Notice ----- This e-mail and any attached documents contain confidential information belonging to the sending entity, Rex Healthcare, and is intended only for the use of the individual(s) or entity(s) associated with the recipient addresses listed in the message header. The authorized recipient of this information is prohibited from disclosing this information to any other party. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of the email and/or attachments is strictly prohibited. If you received this e-mail transmission in error, please notify the sender immediately to arrange for return or destruction of this information. To report abuse or inappropriate use, please email [EMAIL PROTECTED] -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
