[AccessD] Lookup Tables Implementation

James Button jamesbutton at blueyonder.co.uk
Mon Jan 31 03:24:48 CST 2022

Back in the (old) days when I was BD'ing
I would have a table of control info for an app - still do similar for Excel
Several more columns than were needed for the data  so I could include a key of
'data usage'  and  depending on the data type stickit in an appropriate column
Means that an app could easily be conditioned for individual users - with a
record of their own action/options as to the App processing  
Also - access to that set of data could be  limited  via their windows login
and the user data  'added to the department, and corporate logo etc.  details
for things that were sold on. 


-----Original Message-----
From: AccessD
<accessd-bounces+jamesbutton=blueyonder.co.uk at databaseadvisors.com> On Behalf Of
Arthur Fuller
Sent: Sunday, January 30, 2022 11:35 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: [AccessD] Lookup Tables Implementation

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?

AccessD mailing list
AccessD at databaseadvisors.com
Website: http://www.databaseadvisors.com

More information about the AccessD mailing list