Run-time error 429 “ActiveX component can't create object” in Word templates that automate another application (such as Tabs3 PracticeMaster) indicates that Word/VBA cannot create the COM/ActiveX Automation object it is trying to use.
From the provided information, the documented causes for error 429 when automating Office/COM components are:
- A mistake in the application code (for example, incorrect ProgID or using
GetObject where it is not supported).
- A system configuration problem.
- A missing component.
- A damaged component.
On the new machine, this most commonly means the Automation server (in this case, the Tabs3 PracticeMaster COM component that the templates call) is either:
- Not installed,
- Not correctly registered in the system registry, or
- Installed in a way that does not match how the VBA code is trying to create it (e.g., 32‑bit vs 64‑bit mismatch, or different version/ProgID).
Because the same templates worked on the old computer and fail on the new one, and reinstalling Office did not help, the focus should be on the non‑Office Automation component (Tabs3 PracticeMaster) and its integration with Word, not on Word itself.
The general resolution path for error 429 in this scenario is:
- Verify that the Automation server is properly installed on the new PC.
- Verify that the correct bitness (32‑bit vs 64‑bit) of Office matches what the Automation server expects.
- Reinstall or repair the Automation server so that its COM components are correctly registered in the registry.
- If the VBA code uses
GetObject to attach to a class that does not support it, change the code to use CreateObject instead. Note that GetObject cannot be used to obtain a reference to a class created with Visual Basic.
- If access to the object has been explicitly denied (for example, the object is locked or in use), ensure it is not locked and try again later.
If the issue persists after confirming the Tabs3 PracticeMaster integration is correctly installed and registered, the vendor’s documentation or support for Tabs3 PracticeMaster should be consulted, as the error indicates a problem with creating that specific Automation object rather than with Word itself.
References: