|
| 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 |
|
#1
October 11th, 2009, 03:08 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
implemting lookup tables?
Hi,
Is that true that implementing information lookup in MS access is a bad ideas? SF 
|
|
#2
October 11th, 2009, 03:32 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
implemting lookup tables?
On Sun, 11 Oct 2009 09:08:55 +0700, "SF" wrote:
Hi, Is that true that implementing information lookup in MS access is a bad ideas? SF No. It's an absolutely essential part of any substantial Access application. What's bad is using the "Lookup Field" misfeature in Tables. Store data in your tables; put Lookups - Combo Boxes - on your Forms, and do the data entry and editing on the Forms, using lookups wherever they are needed. -- John W. Vinson [MVP]
|
|
#3
October 11th, 2009, 04:19 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
implemting lookup tables?
Thank for the clarification. It id clear now
SF "John W. Vinson" wrote in message ... On Sun, 11 Oct 2009 09:08:55 +0700, "SF" wrote: Hi, Is that true that implementing information lookup in MS access is a bad ideas? SF No. It's an absolutely essential part of any substantial Access application. What's bad is using the "Lookup Field" misfeature in Tables. Store data in your tables; put Lookups - Combo Boxes - on your Forms, and do the data entry and editing on the Forms, using lookups wherever they are needed. -- John W. Vinson [MVP]
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
