I have a VB6 (SQL 2000) app that has a lot of "preferences" that need to be available througout the use of the program.
What I have now is a preferences class that is created and filled when it is needed - then destroyed.
This is called alot throughout normal use.
What is an acceptable way to store these values for the life of the app? I would like to cut out some database traffic and only get these values if they have changed. The values are only related to the running instance of the app so I dont need to worry about other users changing values.
I was considering using a global instance of the prefernces class? Is this bad practice?