logo
search
Office for Mac Issues

Fix Excel for Mac Error 400 When Importing UserForms (.frm and .frx)

Huma Ashraf ChHuma Ashraf Ch Oct 12, 2026 868 views

Question details

The user is experiencing an Error 400 when attempting to run a UserForm in Excel for Mac because the application fails to import the associated .frx file containing graphics and layout data.

Fix Excel for Mac Error 400 When Importing UserForms (.frm and .frx)
Product
Microsoft Excel for Mac
Device & OS
macOS
Scenario
Importing a UserForm exported from Excel for Windows into the Excel for Mac VBA Editor.
Observed behavior
Excel for Mac successfully imports the .frm file but ignores the .frx file, resulting in missing graphics and an Error 400 when the UserForm is executed.
Before you start

Ensure that both your .frm and .frx files are saved in the exact same folder location before attempting the import, as the .frm file relies on the relative path to locate its corresponding graphical data.

Solution 1Recommended

Import the UserForm Manually via the VBA Editor

Attempt a clean import of the UserForm files directly into the Visual Basic Editor (VBE). In some cases, the .frm file contains enough embedded data to restore basic elements.

While Mac Excel often struggles with binary .frx files created in Windows, executing a manual import through the Visual Basic Editor is the standard method to bring the code and layout into your Mac workbook.

1
Open the Visual Basic Editor

Launch Excel for Mac, open your workbook, and press 'Option + F11' to open the Visual Basic Editor.

2
Import the File

Go to the top menu and select 'File' > 'Import File...'.

3
Select the .frm File

Navigate to the folder containing your UserForm files. Select the .frm file (the .frx file will not be selectable but must be in the same folder) and click 'Open'.

4
Run and Test

Locate the imported UserForm in the Project Explorer, double-click it to view the layout, and press 'F5' to run it and check if Error 400 persists.

Import the UserForm Manually via the VBA Editor
Cross-Platform Compatibility: Complete compatibility can vary between Mac and Windows versions of Excel. Complex embedded images or custom Windows controls might not render correctly on macOS.
Free Microsoft Office alternative

Try WPS Office for Seamless Spreadsheet Management

If cross-platform VBA errors and missing UserForm graphics are disrupting your workflow, consider switching to WPS Office. It provides a lightweight, highly compatible alternative to Microsoft Office, ensuring your data and standard macros work smoothly across different devices.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
  3. 3. Open Your Spreadsheets: Launch WPS Spreadsheets and seamlessly open your existing .xlsx or .xlsm files without worrying about format conversion.
Highly compatible with Microsoft Excel (.xlsx, .xlsm, .csv) formatsFree and lightweight alternative to Microsoft OfficeFamiliar tabbed interface requiring zero learning curveSeamless file sharing and editing across Windows, Mac, and Linux
microsoft office alternative - wps office

Frequently Asked Questions

What is the difference between an .frm and an .frx file in Excel?

The .frm file is a plain text file that contains the structural code and properties of your UserForm. The .frx file is a binary file that stores graphical elements like embedded images, custom icons, and specific layout data associated with that form.

Why do I get Error 400 when running a macro in Excel for Mac?

Error 400 is a generic VBA error indicating a failure during macro execution. On a Mac, this frequently occurs when a UserForm tries to load incompatible Windows-specific objects, missing references, or graphical elements from an .frx file that macOS cannot properly process.

Can I open Excel Windows UserForms on a Mac without errors?

Basic UserForms without complex graphical elements usually transfer perfectly. However, forms containing custom Windows controls, heavy embedded images (.frx dependencies), or Windows API calls often require manual adjustments in the Mac VBA Editor.

How can I transfer a UserForm without losing images?

Ensure both the .frm and .frx files are exported into the exact same folder on the source machine. If transferring to a Mac still fails, the most reliable workaround is to remove the images in the Windows environment, import the plain form on your Mac, and manually re-add the images natively using the Mac VBA Editor.