Re: Logical data design, Pick style
- From: mg.ryder@xxxxxxxxx
- Date: 30 Mar 2006 01:19:45 -0800
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
.
- Follow-Ups:
- Re: Logical data design, Pick style
- From: Excalibur
- Re: Logical data design, Pick style
- References:
- Logical data design, Pick style
- From: dawn
- Logical data design, Pick style
- Prev by Date: Re: UniBasic code that should work
- Next by Date: Re: Logical data design, Pick style
- Previous by thread: Re: Logical data design, Pick style
- Next by thread: Re: Logical data design, Pick style
- Index(es):
Relevant Pages
|