🚀 Developers App Helper - part 1
Today, I am starting a new series of articles for DEV Functions. In each part, I will introduce you to small but extremely useful helpers that will make your databases more professional, convenient, and flexible. The Developers App Helper
🎯 What is behind it?
In my projects, I have developed a series of functions that are used in the area of applications and databases. They are small, effective, and can be easily integrated into existing VBA solutions.
Today, we will focus on the following functions:
✅ AppCreateDesktopShortcut
Creates a shortcut to the current database on the desktop. With its own icon,
command line arguments, or description text
✅ AppCreateStartMenuShortcut
Creates a shortcut to the current database in the Start menu. With its own icon,
command line arguments, or description text
✅ AppDeleteStartMenuShortcut
Deletes an existing shortcut in the Start menu.
✅ AppAddTrustedLocation
Adds a trusted storage location to the Access registry. A description can also be added if you want.
✅ AppSetProperty
Creates or changes an Access database property (DAO).
✅ AppDeleteProperty
Deletes an existing database property.
✨ Why are these features so handy?
A shortcut on the desktop or in the Start menu makes your application look like a “real” app – immediately accessible, professional, and user-friendly.
With the AppSetProperty function, you can even dynamically change important properties of your application:
- AppTitle → The window title is customized, e.g., “Test Environment,” “Production System,” or “Demo Version.”
- AppIcon → Give your application its own icon – this immediately makes it look more professional.
- ByPass → Controls whether the Shift key bypasses the security functions at startup. Ideal for differentiating between developer and end-user access.
🔄 Why change properties at runtime?
Here are a few exciting use cases where it makes sense to dynamically control app properties:
- Multi-tenancy: Do different customers or departments work with the same application? Change titles and icons at runtime so that everyone knows immediately which environment they are in.
- Test vs. production: When starting from a test database, it should be immediately clear that it is not the production environment.
- Context-dependent functions: A different title or a special icon could appear for certain user roles (e.g., admins).
- Project phases: During a rollout phase, you can set the right expectations with a customized title such as “Beta” or “Pilot version.”
In short: You give your database a flexible face – appropriate to the situation.
🧪 Just give it a try
You can try out the features directly using my little testing form. This makes it easy to get to know the effects step by step – and, of course, to adopt them for your own application.
Do you do a lot of development with Access? Then give it a try – I look forward to your feedback or ideas for further features! 🚀
You will find the detailed description and all instructions directly in the code - well documented as usual.
DOWNLOAD
Version: 1.0
