[AccessD] Lookup Fields in Table Design

>'Drew, develop this, but don't use API's because their vauge and
mysterious, and don't use indexing, because it'll bloat the database and
it's just a lazy way for developers to speed up their applications, instead,
roll your own indexing', I'd look at him like he was nuts!

If I said that I would hope that you would slap me around a bit.

John W. Colby
www.ColbyConsulting.com

-----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 3:46 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Lookup Fields in Table Design


Hit below the belt.  Charlotte, back to your corner! LOL

Actually, I think I'd rather be known as the Crusador of the Self Taughts.
I like to challenge the 'bad practice' stuff a lot, because I have found
that a lot (certainly not all) is based solely on developer limitations, not
actually system limitations.  If you look at the sides I have been on, I am
rarely saying people MUST do something, but instead, they CAN do something,
if they choose to.  Like the bound/unbound debate.  I was simply pointing
out that there is nothing wrong with an unbound form.  There are times where
it is easier to use an unbound form.  There are also times where it is
easier to use a bound form.  But saying that unbound forms are bad practice,
or a waste of time, is not right (it doesn't apply to bound forms either).

Also, like the original thread, Frameworks are handy.  They aren't good for
every situation, but they certainly can be useful in other situations.  JC
has done a superb job of bring light to the subject, and has written
excellent code examples.  I must admit I don't prefix my Class objects, and
variables the same way, but if JC gave me code, and said it will do what
it's supposed to, I would have absolute faith that it would.  If JC needed
me to write code for him, and said, 'hey, use my naming convention, and work
within my framework', I would have no problem doing so.  Then again, if JC
said 'Drew, develop this, but don't use API's because their vauge and
mysterious, and don't use indexing, because it'll bloat the database and
it's just a lazy way for developers to speed up their applications, instead,
roll your own indexing', I'd look at him like he was nuts! (Not picking on
ya JC....LOL)

Drew