[AccessD] Framework Discussion - set up question

We're gonna need a BIG bag of marshmallows!  Their side is just burning up.
Haven't actually added a valid/proven argument yet! LOL

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Thursday, March 25, 2004 4:16 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Framework Discussion - set up question


I want to know why he's changing the table names? ;) Oh my gosh, what a
horrible mess you might create all the way down the line -- not just with
lookup fields. 

<fire's hot, just about ready -- Drew, hand me a marshmallow, would ya?>

Susan H. 

Okay, for number one, let's drop that.  It's a pointless argument.  If you
want to argue that using Lookups adds confusion, then I would REALLY hate to
see your table designs.  Have you ever tried to explain a many to many table
to a 'user'?  Trust me, they'll pick up what a 'lookup' field does a LOT
faster.  And if you aren't using things like many to many tables, because
users could get confused, then you are not normalizing your data.  See how
this is a BAD argument to try to defend against?

Now for number 2.  You can't hack a feature with a 'feature creep' agrument.
Feature creep can affect anything in a bad way, however, if you are getting
paid by the hour, or are doing contract work, Feature creep means more
money! LOL


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com