Full Version: Creating "Options"
UtterAccess Discussion Forums > Microsoft® Access > Access Q and A
KevMuskoka
I'm going to be looking at putting "Options" into my Access Database, basically to simulate a program's options.

I want to know if this is possible, more information below to hopefully help in what I want to do.

I currently run a database that works for the specific company. However the program will be put into another company, which will have some different options. When creating updates I don't want to have to update two separate databases, I'd rather just have an "option" table using a DLookup to get each option.

For example, automatically e-mail a report to a company executive. In the options table (which would be configurable by the user), I would set the e-mail address to send this report to. When the "EMAIL" button is clicked, it would do a DLookup to look in a tblOptions, goto row=56 and grab the e-mail address from a "value" field.

The reason I use row=56, I might have quite a few options in this table. row=55 could be "Use E-Mail" Yes or No (which may not even send an e-mail).

Is this not using the database properly ? Or does it sound okay ?

Kevin
strive4peace
you are on the right track with thinking about how you would make certain features more general. As for email addresses, it would be better to have the flexibility to send anyone a report through email -- what about a list of email addresses as a combobox on the report menu -- and when a report is chosen, the code will determine the person (or list) identified to get the report -- as opposed to hard-coding an email address in for particular reports.

fyi

in this thread, there is a library of code - basic procedures
http://www.utteraccess.com/forums/showflat...;Number=1036232

one of them is EMailReport

---

back to the default value concept.

Just as your data is structured, your default values will be too -- if you will have that many of them. In some of my databases, I have several defaults tables -- I usually have at least one in every database for the basics such as version.

I name the tables this way:

usys_defaults

"usys" means "user-system" and will be hidden unless system objects are showing
KevMuskoka
Thanks, I'll have to do some experimenting with this. I'm working on some other "issues" at this time, but I will definitely need to look at the options in the next month or so.

Thanks again.

Kevin
strive4peace
you're welcome, Kevin wink.gif happy to help
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.