How to Fix Outlook VBA GetRules Errors with Office Version 16.0
Question details
The user encounters a failure in Outlook VBA when executing the olStore.GetRules line, despite having Office 2019 installed and Outlook displaying version 16.0.
- Product
- Microsoft Outlook
- Device & OS
- not provided
- Scenario
- Running a VBA script that attempts to access rules from an Outlook Store object.
- Observed behavior
- The macro crashes or returns an error on the olStore.GetRules line because the underlying Store object is missing, removed, or replaced during the session.
Ensure you have saved a backup of your current VBA scripts in a text file and verify that you have administrative access to edit macros in the Outlook Developer tab.
Verify the Store Object Before Calling GetRules
This error primarily occurs because the Store object is removed or disconnected from the default Inbox folder. Adding conditional checks prevents the macro from crashing.
Office 2019 legitimately uses the internal version number 16.0, so this version display is completely expected and not the root cause of the error. The real issue lies in the Store object lifecycle during your VBA session.
If the default Inbox or its Store is removed or replaced while the script is running, calling GetRules on a non-existent object will throw an error.
Open Microsoft Outlook and press Alt + F11 to launch the Visual Basic for Applications (VBA) editor.
In the Project Explorer, find the module and highlight the exact line where olStore.GetRules is executing.
Wrap the GetRules call in a conditional statement to check if the Store object is valid. For example, insert 'If Not olStore Is Nothing Then' before the GetRules command.
Review the preceding lines of your macro to identify any actions or add-ins that might be disconnecting the default Inbox or removing its Store during the active session.
Recreate the Outlook Profile to Fix Store Disconnections
If the Store object is unexpectedly missing without logical code reasons, the Outlook profile or default Inbox routing might be corrupted.
Experience a Smoother Workflow with WPS Office
Troubleshooting complex VBA errors and broken objects in Microsoft Office can be time-consuming. If you are looking for a highly compatible, reliable, and user-friendly alternative for your documents, spreadsheets, and presentations, WPS Office is the perfect solution.
- 1. Download the installer: Visit the official WPS Office website and click the Free Download button.
- 2. Install the software: Run the downloaded executable file and follow the straightforward on-screen instructions.
- 3. Open your files: Launch WPS Office and instantly open your existing Office documents with full formatting retention.
Frequently Asked Questions
Why does Office 2019 show as Outlook version 16.0?
Microsoft retained the internal version number 16.0 for Office 2016, Office 2019, Office 2021, and Microsoft 365. This is intended behavior to ensure backward compatibility for macros, add-ins, and external applications.
What does it mean when the Store object no longer exists?
In Outlook VBA, the Store object represents the physical or remote storage (like an OST or PST file) of a mail folder. If it no longer exists, it means the specific repository your code is trying to access has been disconnected, moved, or deleted during that active session.
How can I prevent the default Inbox from losing its Store property?
Ensure no other background macros, third-party add-ins, or synchronization errors are modifying the default delivery location or unmounting data files while your primary script runs. Always validate the object state before executing commands like GetRules.
