[AccessD] Lookup Tables Implementation

[Susan Harkins]

And Arthur, they might tell you the list is stable and will never change --
until it does. 

Susan H. 


Likewise.  No value lists unless they will never change and only one combo
somewhere.

On Sun, Jan 30, 2022 at 6:51 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> 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.
> Maintaining
> 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
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


--
John W. Colby
Colby Consulting
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com