Re: Logical data design, Pick style

Hi Mike
Your point about static and dynamic data is really important. It does make
a massive difference to the additional audit trails that are required post
ENRON.
Also I should have said in my little rave that I start off by asking the
client boss what he wants and then going to the people who actually do the
job to see what they really do. But now we have moved from database design
to system design, all the same thing to a Pick person but totally disparate
to an SQL type.
Peter McMurray
<mg.ryder@xxxxxxxxx> wrote in message
news:1143710385.219866.97520@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hey Dawn,

Thats way too complicated. I start from the end and work back. What
does the user want to see on the "report / invoice / statement /
document / screen" and work back from that to define how the data will
be stored and how the relationships should work. The only real grit is
deciding between dynamic and static data because, from my perspective,
these should be stored in different tables.

The bigger the numbe of files, the more complex this becomes. When it
becomes too complex I use MS Access to scope the tables and produce the
entity diagrams because it has a really nice tool for doing that!! (see
Access does have its uses<g>)

Mike



.