'%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)
How to Fix Excel Run-Time Error 5 on Windows Computers
Question details
A user encounters Run-Time Error 5 when opening an XLSM macro file on a different computer, despite the file working correctly on the original machine.
- Product
- Microsoft Excel
- Device & OS
- Windows
- Scenario
- Sharing and executing VBA macros (.xlsm) across multiple computers with potentially different system setups.
- Observed behavior
- The macro triggers a Run-Time Error 5 on a specific user's computer, likely due to VBA code compatibility, missing references, or 32-bit versus 64-bit architectural differences.
Before making changes, verify that macros are fully enabled in the Trust Center settings on the affected computer, and ensure the user has the necessary permissions to access any network folders referenced in the VBA code.
Isolate the XLSM File and Verify Excel Architecture
Determine if the issue is specific to the workbook itself or caused by differences between 32-bit and 64-bit Excel installations.
Run-Time Error 5 (Invalid Procedure Call or Argument) frequently occurs when a macro written on a 32-bit version of Excel is executed on a 64-bit version without proper API declarations, or when a file becomes corrupted during transfer.
Send a different, known-working XLSM file to the affected user. Have them open it and run a basic macro to see if the issue is isolated to a specific workbook.
On both the working and non-working computers, open Excel, click on 'File' in the top ribbon, and select 'Account' from the left-hand menu.
Click the 'About Excel' button. Note the exact build number and check whether the installation is 32-bit or 64-bit (listed at the end of the first line in the dialog box).
If the original PC is 32-bit and the affected PC is 64-bit, open the VBA Editor (Alt + F11) and update any Windows API 'Declare' statements by adding the 'PtrSafe' keyword.
Debug the VBA Code for Missing References
Use the built-in VBA debugger to locate the exact line of code causing the error and check for missing libraries or invalid paths.
Try WPS Office for Seamless Spreadsheet Compatibility
If you frequently encounter version conflicts and architecture errors in Microsoft Excel, consider switching to WPS Office. It provides a highly compatible environment for your spreadsheets with a familiar interface, reducing the hassle of cross-device file sharing.
- 1. Download the Installer: Visit the official WPS website and click the download button to get the latest WPS Office installation package.
- 2. Install WPS Office: Run the downloaded executable file and follow the simple on-screen instructions to install the suite on your computer.
- 3. Open Your Spreadsheets: Launch WPS Spreadsheet and directly open your existing Excel files to enjoy seamless editing and formatting compatibility.
Frequently Asked Questions
What does Run-Time Error 5 mean in Excel VBA?
Run-Time Error 5 indicates an 'Invalid Procedure Call or Argument'. This usually happens when a macro passes an unacceptable value to a function, attempts to call a function that is not supported by the current Excel environment, or tries to access a file path that does not exist on the computer.
Why do macros work on a 32-bit Excel but fail on a 64-bit Excel?
64-bit versions of Excel require VBA code that calls Windows API functions to be explicitly updated for 64-bit environments. You must modify the code to include the 'PtrSafe' keyword in Declare statements and use the 'LongPtr' data type for pointers and handles to avoid memory access errors.
How do I check if my Excel is 32-bit or 64-bit?
Open Microsoft Excel, click on the 'File' tab, then select 'Account' at the bottom of the left sidebar. Click the 'About Excel' button. A dialog box will appear displaying the version number, and it will clearly indicate whether it is 32-bit or 64-bit at the end of the very first line of text.
