I'm pretty sure this is what I began with when I set up the product catalog portion of my db. It is still structured to show the "orders" and "orderdetails" tables. I will have to add fields to accomodate my scenario, but it sounds like that may be my best alternative.
So... in the "order details" level, would the database create multiple records for the same order if needed? Does it just know to do that as part of the server behavior? Or do I need to add something to make that happen?
One more question. Would you think it would be a bad idea just to put all of the customer info in the "orders" table rather than create a third level? I just want to keep it as simple as possible so we don't screw up orders internally.
My goal at this point is NOT to have a situation where someone can maintain an account at my site.