What do experienced programmers find the most efficient way to handle
user settings.
Currently I have 4 tables which allow various clients to customize my
program to work for them, tblAcademicSettings (fields),
tblBillingsettings (32 fields), tblGraphical (23 fields), tblOwner (33
fields).
There is one record for each table. Admittedly, some of the fields
never change once set up, but many are there to allow the user to make
later changes in how the program works for him.
Til now, I do lookups every time I need info from one of the tables.
Definitely slow, and often causes "Can't open any more databases".
Clearly a better method is needed.
Before I start running benchmarks, I'm hoping folks here can weigh in
on their preferences.
Can I just open all these tables & keep 'em open?
Am I better off setting up public variables and loading the table info
into them all on load of the Switchboard? I will, of course, need to
update the variables any time the forms with this info are changed, but
I'd have to do that with open tables as well.
Or, should I store these values in my own folder in the Registry? Is
this risky?
Or, is there a better way?