[AccessD] Framework Discussion - set up question

In Line:

For one thing, it can cause a lot of confusion among users who insist
they have entered a particular string in a field and don't understand
why they can't find it in a query.  No, Virginia, the query isn't
broken, but you're looking for the displayed value instead of the actual
value, which is numeric!

Good Point. But then again, many "normal" people have no idea what a "query"
is.
-But chalk one up for the nay-sayers.

Why use something that shouldn't be needed and
is just a lazy programmer's crutch in the first place.  Users should NOT
be looking at tables and developers should know better.

Unless its part of the specification that they can.
-Uneccessrily flamatory one penalty point for the nay-sayers ;o)

They also add a level of querying that affects the performance and bloat
of the database.  Each one of the innocuous looking lookups is actually
a SQL statement retrieving information from another table.  Toss with a
handful of "useful" automatic subdatasheets, and your performance goes
out the window.

-But chalk another one up for the nay-sayers.

score 2: nay-sayers 0: sayers

Charlotte Foust