If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Using Lookup fields
typogarphical - sounds like a new species of dinosaur or shark?
Jeanette Cunningham "John W. Vinson" wrote in message ... On Wed, 28 Jan 2009 23:36:48 -0500, strive4peace wrote: Excellent dissertation, Albert! ... although I am still wondering what a 'reocrdsets' is smile A typogarphical error I presume. -- John W. Vinson [MVP] |
#12
|
|||
|
|||
Using Lookup fields
"John W. Vinson" wrote in message
... On Wed, 28 Jan 2009 23:36:48 -0500, strive4peace wrote: Excellent dissertation, Albert! ... although I am still wondering what a 'reocrdsets' is smile A typogarphical error I presume. .... or a speeling mistook |
#13
|
|||
|
|||
Using Lookup fields
It is fine to use them and as long as your database follows relational
design there should not be any issues. Instead of having lots of lookup tables it is possible to put all lookups into one table. For FREE Access ebook and videos click here http://access-databases.com/ebook On 28 Jan, 02:59, DumbWithData wrote: Is it bad design to use the lookup field data value in tables? *If so, why? * Is it better to use these in forms? |
#14
|
|||
|
|||
Using Lookup fields
"troy23" wrote in message
... It is fine to use them and as long as your database follows relational design there should not be any issues. Instead of having lots of lookup tables it is possible to put all lookups into one table. And your comments on lookup *fields*? And please don't spam this NG. |
|
Thread Tools | |
Display Modes | |
|
|