Lookup Fields: Was: RE: [AccessD] Fr at mework Discussion - set up q uestion

Charlotte Foust cfoust at infostatsystems.com
Fri Mar 26 13:49:56 CST 2004


I think that's where some of the argument comes in, Drew.  Those of us
who work entirely in Access FEs have a different perspective on some of
the things you discount.  As for bloat, that is a major issue in Access
FEs, since that's where all the queries execute and all the temporary
queries cause the bloat.

Charlotte Foust

-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] 
Sent: Friday, March 26, 2004 11:46 AM
To: accessd at databaseadvisors.com
Subject: RE: Lookup Fields: Was: RE: [AccessD] Fr at mework Discussion -
set up q uestion


If you get right down to it, MOST of my development is in VB 6 or ASP,
for front ends, so Access forms aren't that big a deal for me.  But I do
develop Access FE's from time to time, and have yet to see the harm in
using Lookups when necessary.  Plus, with VB or ASP front ends, it's
handy to go in and see the data.  Putting lookups in, allows me to look
at applicable information in the tables, instead of pk's, which have no
real meaning to what I am looking for. (Most of the time.  sometimes I
do want to see the pks, so then I just turn the lookups off!)

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Francisco H
Tapia
Sent: Friday, March 26, 2004 11:02 AM
To: Access Developers discussion and problem solving
Subject: Re: Lookup Fields: Was: RE: [AccessD] Fr at mework Discussion -
set up q uestion


DWUTKA at marlow.com said the following on 3/26/2004 8:38 AM:

>Let me ask you a question though, because you and I have agreed on a 
>lot of other things before, so I'm a little shocked on your position on

>this.  If you have an Address table, (for US clients....for this 
>example), and you want to get the two letter state abbreviation, do you

>simply give them a textbox, or do you give them a combo that builds 
>itself from a 'State' table?  I go with the state table.  And since I 
>may have multiple forms based on that table, I usually use a Lookup 
>field, so that when I build the form, that combo is predefined.
>  
>
This particular example is kind of bad (for me), because I try to create

one form for one purpose, thus the data entry screen for addresses is 
done on one form, thus end users use the same form to add/edit addresses

that require the combobox that points to a table of states.  So yes, 
that's a lookup on the "FORM" not the base table.  That has no point...

so I have one need for the state combobox.. why build it at the table 
level?  and I encourage for my users to type in the zipcode first so 
they don't usually search for states... :)

-- 
-Francisco


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



More information about the AccessD mailing list