Lok Up Fields???

C

CoachBarkerOJPW

I have seen it on here many times and I was just curious, exactly what is so
bad about using a look up field in a table, especially if the table has many
fields that contain foreign keys? Isn't it easier to open the table and see
the what is being stored in the field rather than a foreign key?
 
C

CoachBarkerOJPW

Thank you, I was under the impression that because it was a query based upon
maybe two fields, and that it was usually only displaying the text that it
did not alter any other properties.
--
Thank you very much
CoachBarkerOJPW


Roger Carlson said:
See this link:
http://www.mvps.org/access/lookupfields.htm

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
Click to expand...
 
J

John W. Vinson

Isn't it easier to open the table and see
the what is being stored in the field rather than a foreign key?
Click to expand...

Yes. That is the ONLY virtue of the Lookup Field. (Well, there's a small
additional virtue, a lookup field inserted onto a Form creates a Combo Box).

However, editing data in table datasheets is generally a bad idea. Forms are
much more powerful and flexible. As noted in the link, the Lookup Field makes
you pay for these two small advantages with several much larger DISadvantages.

John W. Vinson [MVP]
 
C

CoachBarkerOJPW

Well I would never considering a table directly, but at times when I have had
a problem with data in a table, it is nice to open the table and not have to
compare the values in two tables to see if the data is what I thought it was
supposed to be.
 
T

Tom Wickerqueer

there is nothing wrong with lookup fields

if you used Access Data Projects then you could use Query Analyzer in order
to 'see the data without lookup fields'


this feature isn't available with MDB
 
Top