Lookup fields in tables bad?

[David W. Fenton]

The "my mom" part was metaphorical, but your post didn't cover the
real example I gave......there are lots of databases out there
where there is no developer, and which are created in minutes and
used by only on or two power users. The don't look at data in
table views, but often look at it query views, setting completely
different sort and filter criteria on different fields with each
use.

I did mean my response to address that scenario -- those kind of
uses should create forms to edit their data. Period. It's the only
way to do it right in the long run.

And, yes, I know it's tilting at windmills to fight this fight in
that user population, as they are going to use the tools MS has
provided (and encourages the use of by their implementation). I
think MS is wrong in what it has implemented, and does a terrible
job in its sample databases of implementing "easy" things that are
really bad design in the long run.

The fact that people will use it and feel like it's useful does not
change the fact that there are ways to do their work that are no
harder to implement and don't have the long-term downside.

 

[Robert5833]

Hi John,
Thank you for the replies; yours and others have helped me a lot. I've tried
to reply in sequence with this thread but I guess I'm not smart enough to do
that yet...

Is there a discussion group for that?

Best regards,
Robert

 

[Allen Browne]

Great response. Good to know it's all helpful.

Hope you're over the 'flu quickly.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Hi Allen; et al,

Thanks so much for the great outline on this subject, and I appreciate
very
much your taking the time to help me understand.

I would have replied sooner, but I’ve been down hard with the flu.

[snip]