DWUTKA at marlow.com
DWUTKA at marlow.com
Thu Mar 25 15:58:43 CST 2004
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 Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Francisco H Tapia Sent: Thursday, March 25, 2004 3:19 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Framework Discussion - set up question DWUTKA at marlow.com said the following on 3/25/2004 11:53 AM: >What's impractical about Lookup stuff in a table design? > > 1) When you query the table you're querying against some text... instead of ID's... while there is no one right way.. you're adding confusion. 2) when you want to add additonal columns so that the sub table can have it's own set of attributes because the system has "grown" you'll need to revisit the table to make the changes for the FE, but if you're using some sort of BE/FE setup then you can't do anything until all the users are out :) -- -Francisco -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com