Rabu, 19 Oktober 2011

Re: [MS_AccessPros] Persistence Framework

 

I got that one too :)  Thanks, Duane!

~~~

Mark (is that your name?): you said, "Comments/suggestions greatly appreciated."

Access is a database -- use tables for structured data.  I also use database properties since they persist once they are set, even when the database is closed.  Procedures read the structured information, based on the user and other parameters, and set relevant database properties.  This way, Open events on forms and reports can check permissions against the database properties and decide whether to (1) open (2) prompt for password, or (3) cancel and give user a message they don't have permission.  the Open event can set colors, loop through controls looking for values in the TAG property and set properties accordingly.  Some of the apps I have built modified label captions depending on language or application module (such as in a generic report menu that swaps colors, report list, and criteria choices based on how the user got there)

Your use of terminology makes me wonder if you are coming from Visual Studio ...

What kind of an application are you building?

Warm Regards,
Crystal

Access Basics by Crystal (Bill Mosca's site)
http://thatlldoit.com
Free 100-page book that covers essentials in Access

 *
   (: have an awesome day :)
 *

________________________________
From: Bill Mosca
Duane - What a clever idea! Thanks for sharing.

Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile/Bill.Mosca

--- Duane Hookom wrote:
>
>
> Mark(?),
> "application's important settings" have you considered running the database documenter? The results of the documenter are saved temporarily in a table in a wizard database in your profile. I'm using Access 2007 at the moment so my table is doc_tblObjects in C:\Users\ushookomd\AppData\Roaming\Microsoft\Access\ACWZUSR12.ACCDU.

> In the past, I have run the documenter with all of my "application's important settings" and then imported the doc_tblObjects table into my application file or another file. The table has only a few fields and is quite normalized so you have to play with it to make it useful.

> Duane Hookom
> MS Access MVP
>

>
>
>
> To: marksimms@...
>
>
> 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.
>
>

[Non-text portions of this message have been removed]

__._,_.___
Recent Activity:
MARKETPLACE

Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.

.

__,_._,___

Tidak ada komentar:

Posting Komentar