[AccessD] Lookup Tables Implementation
ssharkins at gmail.com
Sun Jan 30 19:36:17 CST 2022
And Arthur, they might tell you the list is stable and will never change --
until it does.
Likewise. No value lists unless they will never change and only one combo
On Sun, Jan 30, 2022 at 6:51 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> A lot depends on how mutable the values are over time.rather than how
> many values there are.
> With a lookup table, you can use a left join to it for queries/
> reporting and so include all possible categories.
> Maintaining a lookup table means you only do it in one place.
> maintaining value lists means that you have to edit every control on
> every form that uses the values.
> consistency can be a nightmare.
> As a general rule, I don't use value lists.
> On 30 Jan 2022 at 18:35, Arthur Fuller wrote:
> > The basic choices are a physics table and a Value List. I am
> > guessing, and with no evidence, that if the Lookup has only a dozen
> > rows or fewer, that it is pointless to create a table, but am also
> > suspecting that there is overhead involved that I may not be aware of.
> > Any opinions on this topic?
> > --
> > Arthur
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> AccessD mailing list
> AccessD at databaseadvisors.com
> Website: http://www.databaseadvisors.com
John W. Colby
AccessD mailing list
AccessD at databaseadvisors.com
More information about the AccessD