[AccessD] On DB Bloat, Bad DB Design, and various

Arthur -- do you know who wrote the original app? Was it someone in-house
that had to put together something because s/he was told to? Access is as
much a user database as a development tool -- that's what makes it so
alluring to such a wide audience. If the boss tells you the department needs
such and such, and you're not a database developer, know onlyh a little
about Access, you might come up with crap from a developmental perspective
-- but if the crap works... Of course, eventually, they probably are going
to have to call in someone that really understands the issues, but for
awhile -- it works. That's not a bad thing -- and I don't know that that's
even the situation in your case Arthur -- but I think it happens a lot. 

And a lot of so called developers produce crap -- especially the geniuses in
other areas that think Access is a toy and that anyone can "do it." Those
folks irritate me because invariably their stuff is inefficient and
laborious -- but it "looks" difficult and that's what people expect to see,
so they must know what they're doing, right? :) 

My personal favorite is developers that claim it can't be done without code.
Yeah... Right... 

But, the crap issue -- it's why I don't do it -- I'd produce more crap than
good stuff in today's environment. I can sling out little stuff with the
best of you, but once you get into the multi-user issues, I'd rather visit a
dentist. 

Susan H. 

I don't think certs are the answer either Arthur--it is too easy to get a
certification, and they push you through to fast. You don't even have to
produce anything original to get a cert--just do their stupid exercises in
the back of the chapters. And, I have seen certified people, both
programmers and network admins, do stupid stuff.