[AccessD] Design Considerations - Was: Table Structure Ideas

Wow Darryl, I could not agree more. This was really wise advice and
countenance.
However, it doesn't work in all organizations. Some want IMMEDIATE
results....and sadly,
they don't care about the quality. I HATE THAT APPROACH.

In my last (and awful) contract, I would think of a design, implement it,
and then and ONLY THEN would the manager berate me and say "why didn't you
do it this way ?".
I was constantly re-writing code.

>
> Great post Don - I am going to file this one as I have seen and
> experienced many of these issues and questions in my professional life.
>
> As for "Is it ever appropriate to "out-think" the client and deliver a
> system that they didn't ask for and don't know they'll be needing?"
>
> For many clients I have worked with it is nearly always this way.  It
> is not their fault though as they think of data in terms of the front
> end UI forms (almost like MS Word visual frame) and have little to no
> understanding of data integrity, scalability and the ease of updating
> for future changes - and there are always changes.
>
> It is usually worth spending a fair bit of time talking to the client
> about their needs and watching how folks use the interface before
> starting.  Having a deeper understanding about how the data is used and
> how it integrates into their organisation and systems usually pays big
> dividends.
>
> As ol' Abe Lincoln was reported to have said "Give me six hours to chop
> down a tree and I will spend the first four sharpening the axe."
>
> So I would say 'yes' in the majority of cases.  Trust your experience
> and instincts - make the front end just as the like it, but make sure
> the back end is built as you need it to be, not as the client thinks it
> should be - they are usually completely out of their depth here.
>
> Cheers
> Darryl
>