Sales db design...
From: Me <no-address_for_spammers_at_no-address.com>
Date: Thu, 23 Feb 2006 09:58:39 -0500
Message-ID: <dtkij5$56oc$1_at_news3.infoave.net>
Hi all,
Date: Thu, 23 Feb 2006 09:58:39 -0500
Message-ID: <dtkij5$56oc$1_at_news3.infoave.net>
Hi all,
I have a simple question, really.
I'm trying to build a database to handle sales. I've been looking around
at examples, both on the net and example db's such as "Northwind" that
MS puts out as an example, and I see that it's common practice to handle
line items for *all* invoices in *one* table and then retrieve line
items for each invoice by the invoice number column that's included in
the line item table. With numerous line items on each invoice this will
obviously generate an absolutely *massive* table eventually, assuming
that the company in question does a high sales volume. Seems counter
intuitive to me, but I can't think of a better way to do it. Is this