[AccessD] Lookup Fields in Table Design

LOL.  I am an unbounder.  Doesn't mean I don't use bound forms, I just find
that most of what I do fits the unbound world a lot better.  Let's not get
this one rolling again.  It was pretty much agreed last time that both
methods have their time/place/usage.  Neither is better, and neither is a
'bad practice'.

Now if we could just get there with these lookup fields! LOL

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of David McAfee
(Home)
Sent: Friday, March 26, 2004 3:09 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Lookup Fields in Table Design


No Drew, its more like you shouldn't use bound forms, only unbound! :P

<hey, its Friday>

David

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
DWUTKA at marlow.com
Sent: Friday, March 26, 2004 12:29 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Lookup Fields in Table Design


And like I said to Gustav, that is EXACTLY why I got into this thread.  You
can't really understand something, if you can't challenge stuff with a 'why
not?'.  And if the answer doesn't really wash, you need to drill down until
you find the real 'why not', or until you find that you 'can'.

It's like the SendKeys issue.  Yes, Sendkeys has a bug, which causes the
Numlock key to change state.

WAY too many people say that you should NEVER use the SendKeys statement,
unless it's a dire emergency.
<snip>
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com