bsams
04-21-2003, 12:53 PM
My app has certain parameters that can be user customized. I have a table in my access db that holds these parameters. Is this a good idea, or should I use the Registry to hold these?
My first thought on this was that it would be nice to have as few supporting files as possible. It would be great if I could only have two files - the exe and the db.
Robse
04-21-2003, 01:13 PM
My app has certain parameters that can be user customized. I have a table in my access db that holds these parameters. Is this a good idea, or should I use the Registry to hold these?
My first thought on this was that it would be nice to have as few supporting files as possible. It would be great if I could only have two files - the exe and the db.
Having a database just for some parameters seems mighty overkill to
me. What are these parameters?
Also consider that you'll have to include some database library in
your setup routine, e.g. MDAC. I personally avoid using the registry.
Have you looked at *.ini files?
bsams
04-21-2003, 01:18 PM
My program is simply the frontend to a database. The database already has about 40 tables in it so I thought one more for certain preferences wouldn't hurt.
I'm just wondering if there is some great reason to use the registry as opposed to 1) another table in my db, 2) an ini, 3) something else.
Robse
04-21-2003, 01:24 PM
Well if your program is a frontend to the db anyway...
A reason to use the registry could be the ease of making information
known to the operating system or other applications.