On Thu, 13 May 2010 22:21:01 -0700, Terry Cano
wrote:

Yep that's what I do then I think of the relationships I need (many scenerios
and move the relationship around) before I start the table.

Don't get too hung up on the "scenarios" (different kinds of data display I'm
guessing).

Instead, think about the Entities - real-life people, things or events -
represented by your database. Each kind of Entity gets its own table. For
example a Customer is one kind of entity; a Product is another; a Sale is yet
another.

Then identify how the tables representing these entities are related:

Each Customer may have zero, one or many Sales
Each Product may have zero, one, or many Sales
Each Sale involves one and only one Customer and one or more Products

--

John W. Vinson [MVP]