[AccessD] Framework Discussion - set up question

Woa! Another passionate comment!

One point sayers!

Actually I won't count my dittos here: If its going to be a potential
problem when you pick up the job, just run code to eliminate them all.

Score: 2 nay-sayers 2.5 sayers

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
DWUTKA at marlow.com
Sent: Thursday, March 25, 2004 1:59 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Framework Discussion - set up question


I don't get that 'main' argument.  How could you NOT know that they are
there?  Granted, if I looked at a table, and saw that for Customer, it had a
first name, instead of a CustomerID number, that I might be a little
suspicious.  However, entering that field, in the table, would show that
it's a combo box, thus a lookup field, and I would know what is ACTUALLY
stored within that field is a Long Integer foriegn key. (Or should
be....LOL).

Lookups are just part of Access' table design, and are relatively irrelevant
when you use Access strictly as a BE.  It's just like opening a table in
datasheet view, and widening a column.  It doesn't change the field size for
that field, it just changes what you see when you are in datasheet view.
Access remembers that too.  (Still like to know WHERE it remembers it) But
is that going to affect anything using that .mdb as a BE? No.

I would really like to hear a solid reason for not using this.  I'm
definitely in the 'Use Lookup' camp otherwise.

Drew