I have a table that is populated and I'm trying to make a field on it a "lookup" type. After closing the lookup wizard, the field remains "text". I'm thinking this is not allowed. How can I get around this?
Thanks,
I have a table that is populated and I'm trying to make a field on it a "lookup" type. After closing the lookup wizard, the field remains "text". I'm thinking this is not allowed. How can I get around this?
Thanks,
Is your issue actually resolved, thread is marked 'solved'.
Most advanced developers do not set lookups on tables.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
thanks for the follow-up; although the type continues to show as "text", the lookup values are available in the datasheet view; thus the closure
what is the best practice for having a set of lookup values? in the form as opposed to the table? why is a table not considered a good place for this? please advise.
thanks again.
Thanks; so what's the alternative to lookup fields? a lookup table?
I have never set lookup in tables and have never used the Lookup field type wizard. I set lookups with combo/list box controls on form. Data comes from tables or for very short standard list for RowSource, I build ValueList. For instance, for M or F choices, would set RowSourceType to ValueList and the RowSource would be: M;F
http://access.mvps.org/access/lookupfields.htm
Are you using multi-value field? Is that why you are setting the lookup? I don't use multi-value either.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Thanks; I would be looking at multi-value lists as well but for now I'm just looking for standard values such as Active, Inactive, etc. So, I'm going to stay away from lookups in tables and put them in forms instead using either a table as source or a value-list. I guess the rationale for not using lookups in tables is to not clutter them with choices and use them just to store values; this makes sense.
Regards,
I believe if you want a multi-value field will have to set the lookup in table.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Oh; Okay; thanks