msimmsx <your name?>
I wouldn't call that a mini-project. That's tons of code-writing. I've done something like that on a small scale. I use a table with the user ID, object name, setting name and setting. I've never had the need to go beyond showing or hiding control hints displayed business rules on a label on one form where list selections were not intuitive such as Tier I, II, III with what each one meant.
As far as application title, that's an easy-squeezy one I do all the time. I just fill in the name in the database properties box and have a function to retrieve it whenever needed.
Color theme? I think this is a grand idea, but one that I would never have the time to develop. But then I create and maintain Access applications about 75% of my work day. Once I set a color theme, that's what the users get. And I control form settings, not my users.
Bill
--- In MS_Access_Professionals@yahoogroups.com, "msimmsx" <marksimms@...> wrote:
>
> I'm about to embark on a mini-project to create a set of functions and tables that will store any application's important settings. The settings could be at the following levels: application (title, color theme, etc), object (default form settings, report settings, etc, object and user (the key of a form's last record viewed, user default value preferences, etc), and finally user-level (initial form to open upon start-up, etc).
> Has anyone attempted this before ? I built a similar framework using SaveSettings, GetSettings but I was unhappy with that result for several reasons: it was registry-based, the settings couldn't be easily cloned or transferred, etc.
> Database properties is another option, but I think it is way too unwieldy for the flexibility of storing and retrieving these settings at all of the various levels as outlined above.
> Comments/suggestions greatly appreciated.
>
Tidak ada komentar:
Posting Komentar