\nIn Microsoft Access, It is a good practise not to use "Lookup" column at Table Level. Lookup feature is best used with Forms.\n<\/p>\n
\nThis would avoid problems such as unable to call the right field from a lookup column, as it usually returns the primary ID key. It would appear that there is no script that can call Table.Column(2), etc. in Access. But Form.Column(2) is doable.\n<\/p>\n
\nIf damage is done, it is best to convert the table's "lookup" fields back to text or other "normal" fields. Using nested Replace() functions in Update Query should be the last resort.\n<\/p>\n
\nThis comes from my experience creating NYGC Student Database System.<\/p>\n","protected":false},"excerpt":{"rendered":"
In Microsoft Access, It is a good practise not to use "Lookup" column at Table Level. Lookup feature is best used with Forms. This would avoid problems such as unable to call the right field from a lookup column, as … Continue reading