Free Lessons
Courses
Seminars
TechHelp
Fast Tips
Templates
Topic Index
Forum
ABCD
 
Home   Courses   Index   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
 
Home > Forums > Access
Back to Access Forum    Comments List
Create Default Settings Upload Images   Link   Email  
Brent Rinehart 
I know Richard has mentioned this before and maybe I should know by now how to do this, but it's not clicking how I should do it. I want to have a table that would store default settings for various forms. such as default path locations, default user choices specific to a user on their front end copy of their database, and more as they come down the road. Would I link to the table or do something like a DLookup to the table to get the value? I would think I would have to go this route because the table would hold settings for multiple forms.

Any links pointing in the right direction would be great thanks
Scott Axton 
Brent you just described exactly how to do it.
Create your table.  It only needs one record.  I call mine dbSettingT.
Add a field in for each setting you want to store.  What ever you want - FilePath, TaxRate, etc. Pretty much any thing that would be "global" to everyone.  The advantage is this is persistent from session to session.

For settings for an individual you could make a "UserSettingT" which would have the user preferences.
You could allow them to choose things like form colors, default printers, etc.
This table would have a record for each user.
Of course this would require that you have individual user logons and a ton more in your code to allow for user settings.

In both cases your DLookup would find the values needed at the time that they are needed.
The other alternative would be to set global variables in a global module when you start up your db.

Pointers to specifics?  Pretty much all of this web site.  The   Lego Pieces   are scattered around.
Richard Rost 
There are so many different ways you could implement this. A simple DLookup from a table would work. If you want to have it unique per user, then add username as a field. If each form has different settings, then just add FormName as a field. It's just really name/value pairs.
Brent Rinehart 
Thanks Scott, I had some ideas just wanted to make sure this was the most efficient way of doing it before proceeding thank you for your help.
Brent Rinehart 
The dlookup for default settings work perfect for storing the default paths to the server. Now this is probably an easy one to but not quite sure how to tackle. I have a search form the is unbound with all the fields unbound as well. where the checkboxes are I would like to create a user default table where they can have those fields be set to default so when they open this form it remembers those settings each time.
Brent Rinehart 

Scott Axton 
Check out this video Filter Records
In the extended cut, Richard shows how to save your filters.  This looks to be what you are describing.

Again, if it is for individuals you would have to have a table that has user level filtering prior to presenting the filters.
This would be doable but more complex.
Brent Rinehart 
I will take a look, I was thinking about save a user table with the front end database the would be specific to that users copy.
Scott Axton 
I just caught the part about the defaults for the check boxes.
Assuming that you have a user logon and are storing that somewhere,
you would need a UserDefaultsT.  In it you would create a 1 to many for each value you want to store for the user.  When the form loads you would have to grab (DLookup) the defaults for that user from your UserDefaultsT for each item you want to preload.
In it you would probably want to use a Composite Key for the User / Checkbox values.

I'm sure there may be other ways that this could be accomplished but this is how I would approach it initially.  Maybe some of the others will chime in with different ideas.
Scott Axton 
The problem with storing the user values in the front end is what happens when you push an update?
Those tables for each of the people would be over written in that update.
Also if you create a new form and need defaults - you would have to go around to each machine (1 to xx) and individually update their front end.
If in the back end you make the change once and put out your update.
Brent Rinehart 
Thank You Scott will give it a crack and see what I come up with thank you for you suggestion always very much appreciated.
Richard Rost 
I agree with everything Scott said. Good job.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Forum.
 

 
 
 

The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Login
My Account
My Courses
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
PCResale.NET
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

LinkedIn
Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 3/28/2024 10:01:41 AM. PLT: 0s