运行时错误429：ActiveX组件无法创建Word.Application对象求助

Hey there, let's sort out that Runtime Error 429 you're facing after reinstalling your system. This error almost always ties to issues with the Word COM/ActiveX component not being properly registered, or mismatches in your Office setup. Here are actionable fixes you can try:

• Re-register Word's ActiveX Component
  Reinstalling Windows often resets COM registrations for Office apps. To fix this:

  1. Find the path to your WINWORD.EXE file. For Office 365/2019/2016, it's usually C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE (64-bit) or C:\Program Files (x86)\Microsoft Office\root\Office16\WINWORD.EXE (32-bit). Adjust the Office version number if you're on an older release (e.g., Office15 for 2013).
  2. Open Command Prompt as Administrator.
  3. Run this command (replace the path with your actual WINWORD.EXE location):

     regsvr32.exe "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE"
     

  You should get a confirmation message if the registration succeeds.

• Ensure Office Bit Version Match
  Excel and Word must be the same bit version (both 32-bit or both 64-bit) for ActiveX components to work correctly. Mismatches will throw this error every time:

  1. Open Excel, go to File > Account > About Excel to check its bit version.
  2. Do the same in Word: File > Account > About Word.
  3. If they don't match, uninstall one of the apps and reinstall it to match the other's bit version.

• Repair Your Office Installation
  Corrupted Office files after reinstall can cause component issues. Run a repair:

  1. Open Control Panel > Programs > Programs and Features.
  2. Find your Microsoft Office installation, right-click it, and select Change.
  3. Choose Quick Repair first (faster) and let it run. If that doesn't fix it, go back and select Online Repair (more thorough, requires internet).

• Check Macro Security Settings
  While less likely, overly strict macro settings can block ActiveX object creation. Test this temporarily:

  1. In Excel, go to File > Options > Trust Center > Trust Center Settings > Macro Settings.
  2. Select Enable all macros (not recommended; potentially dangerous code can run) just for testing. Also, ensure Trust access to the VBA project object model is checked.
  3. Run your code again. If it works, adjust the settings to a safer level once the issue is resolved.

• Test with Early Binding (Optional)
  Your code uses late binding (Dim objWord As Object), which is great for compatibility, but switching to early binding can help diagnose the issue:

  1. Open your VBA editor, go to Tools > References.
  2. Find and check Microsoft Word xx.x Object Library (xx.x matches your Office version).
  3. Change your variable declaration to:

     Dim objWord As Word.Application
     

  4. Run the code. If it works, the problem was with late binding's ability to find the registered component (which the first fix should resolve). If it still errors, the component itself is broken, and the Office repair is your best bet.

Once you've tried these steps, your code should work just like it did before the system reinstall.

内容的提问来源于stack exchange，提问作者Rishi