What is your preferred method of storing application settings for access? Things like Back end location (so an updated FE knows where to look), User Preferences, and other "global" settings. I'd prefer not to hard code them in VBA, because they may need to change at some point. But that is an option.
This is my first time creating an app that will "live" off-site for me. So, I'm trying to be extra cautious, because I won't be there to immediately support it. The BE will reside on a local server, and the FE will be deployed to 5-10 user computers.
So far I can see I have a few avenues:
This is my first time creating an app that will "live" off-site for me. So, I'm trying to be extra cautious, because I won't be there to immediately support it. The BE will reside on a local server, and the FE will be deployed to 5-10 user computers.
So far I can see I have a few avenues:
- Add a table in the back end, with 1 record, and all the settings I would need that are common across users. Then do something else for the user-specific settings.
- Use an .INI file (Still researching if all machines could point to 1 .INI on the server and if this was a recommended practice.)
- Use Registry settings for all of them. I'm not against this, and maybe this is the preferred method?
- Hardcode all of the "global" settings in each FE version. It may be easiest because it's automatic, but if a change is required, I would need time to release a new FE Version. I will be employing a type of FE Auto-update, so future deployment is easier.