Connecting Tech Pros Worldwide Help | Site Map

Lookup Fields

  #1  
Old July 17th, 2006, 04:25 AM
Tim Dunne
Guest
 
Posts: n/a
What is the problem with these? I have never run into an issue with
them yet I hear time and time again that they should never be used. In
the "Ten Commandments of Access" they are said to be the creation of
the Evil One. Is there something specific that happens when using one
or is it just a general guideline for some reason?

  #2  
Old July 17th, 2006, 05:25 AM
tina
Guest
 
Posts: n/a

re: Lookup Fields


if you follow the link in Commandment #2, it'll take you to
http://www.mvps.org/access/lookupfields.htm, which gives a pretty extensive
explanation.

hth


"Tim Dunne" <timmydunne@gmail.comwrote in message
news:1153107183.411344.305540@m73g2000cwd.googlegr oups.com...
Quote:
What is the problem with these? I have never run into an issue with
them yet I hear time and time again that they should never be used. In
the "Ten Commandments of Access" they are said to be the creation of
the Evil One. Is there something specific that happens when using one
or is it just a general guideline for some reason?
>

  #3  
Old July 17th, 2006, 09:35 AM
Nick 'The Database Guy'
Guest
 
Posts: n/a

re: Lookup Fields


Hi Tim,

To tell you the truth I have never used lookup fields, but in there
have been some in some of the databases I have had to, either redevelop
or document, and I have found them to be a bit confusing, unless the
database in question is fully documented, which is a rare thing indeed.

My advise to you would be to stop using lookup fields, and if possible
go back and rejig all your old lookup fields so they work normally.

Good luck Tim,

Nick

Tim Dunne wrote:
Quote:
What is the problem with these? I have never run into an issue with
them yet I hear time and time again that they should never be used. In
the "Ten Commandments of Access" they are said to be the creation of
the Evil One. Is there something specific that happens when using one
or is it just a general guideline for some reason?
  #4  
Old July 17th, 2006, 06:45 PM
Tim Dunne
Guest
 
Posts: n/a

re: Lookup Fields


Thank you guys -- I think I have my answer. My conclusion is that if a
mom and pop store using Access includes lookup fields in their forms,
there is no serious danger if the person making the front end
understands the limitations of these fields. It does seem, however,
that since I am new to this, eliminating lookup fields from my
vocabulary entirely will save me grief down the road with queries and
upsizing to other databases. I am a creature of habit so getting into
the habit of just not using them might be in my and my clients' best
interest.

Thanks again for the information.

  #5  
Old July 21st, 2006, 02:35 AM
pietlinden@hotmail.com
Guest
 
Posts: n/a

re: Lookup Fields


If you don't know what's wrong with them, have someone build you a
database with them, and then ask you to modify it. Biggest PITA I ever
saw. Never use them, and never expected that anyone else would either.
And then i spent like 30 mins trying to figure out why I couldn't get
some really simple thing to work. And then I found it. Not using them
keeps everything obvious.

Closed Thread


Similar Threads
Thread Thread Starter Forum Replies Last Post
Lookup Fields Lance Williams answers 2 June 29th, 2007 01:17 AM
Combining two lookup fields John Smith answers 1 June 19th, 2006 04:45 AM
Need an alternative to Lookup fields google@thaiam.com answers 3 November 13th, 2005 07:01 AM
Should Lookup fields be replaced by table normalisation David Allison answers 2 November 12th, 2005 04:14 PM