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 ?