'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Word for Mac Error 6304 When Opening Old Documents via VBA
Question details
The user is encountering runtime error 6304 in Word for Mac when trying to use a VBA macro to open older Word documents.
- Product
- Word for Mac
- Device & OS
- macOS
- Scenario
- Running a VBA macro to batch-process or open very old Word document files on a Mac.
- Observed behavior
- Word for Mac throws runtime error 6304, preventing the macro from opening the files. This is typically caused by missing file extensions, incorrect macOS file associations, or macOS sandbox restrictions blocking automated access.
Ensure you have full administrator access on your Mac to modify file extensions and adjust privacy permissions, and make a backup copy of your old documents before running batch-processing macros.
Add Correct File Extensions and Fix Associations
Old Mac files often lack extensions. Adding the correct extension and associating the files with Microsoft Word resolves macro access errors.
Older classic Mac OS files used Type and Creator codes instead of extensions. Modern versions of Word for Mac require explicit extensions (like .doc or .docm) to programmaticly open them via VBA without triggering error 6304.
Open Finder and navigate to the folder containing the old Word documents you want to process.
Rename the files to include the proper extension. Use .doc for standard old Word documents. If the file contains macros itself, use .docm or .dotm.
Right-click one of the renamed files, select 'Get Info', and scroll down to 'Open with'. Select Microsoft Word from the dropdown menu, then click 'Change All' to apply this association to all similar files.
Grant macOS Sandbox Permissions to Word
macOS sandboxing may block Word's VBA macros from automatically opening files without explicit user permission.
Try WPS Office for a Seamless Mac Document Experience
If you continue to experience macro errors, sandbox issues, or legacy file compatibility problems in Microsoft Word for Mac, WPS Office offers a highly compatible and lightweight alternative. It natively supports legacy formats and VBA, making document processing hassle-free.
- 1. Download WPS Office: Visit the official WPS website and download the free macOS installer.
- 2. Open legacy files: Launch WPS Writer and navigate to Menu > Open to locate your old document files.
- 3. Edit and save: Easily edit your legacy documents and save them in modern formats like .docx without sandbox restrictions.
Frequently Asked Questions
Why do old Word files lack file extensions on Mac?
Older classic Mac OS versions relied on internal Type and Creator codes to identify file types rather than file extensions. When these older files are opened on modern macOS, they may lack the .doc extension, causing VBA macros to fail.
Can I save a file with macros as a .docx file?
No. The .docx format is specifically designed for macro-free documents. If your document contains VBA code, you must save it as .docm (macro-enabled document) or .dotm (macro-enabled template) to preserve the scripts.
What is a macOS sandbox restriction?
macOS sandboxing is a security feature that limits an application's access to system resources and user data. Because Microsoft Word is sandboxed, its VBA macros cannot automatically open files without you first granting explicit system permission to access that specific file or folder.
