How to Fix Runtime Error 13
As with other runtime errors, runtime error 13 occurs under a number of circumstances and is not generally limited to one specific program. However, runtime error 13 does commonly appear when using macros in Excel as well as when running programs based on Microsoft Visual Basic. Let’s take a look at these two examples of common instances of runtime error 13 and then explore how to fix runtime error 13.
Runtime Error 13 – Type Mismatch
When your computer tells you that a runtime error 13 type mismatch error has occurred in Microsoft Excel 2002, it is telling you about a known bug within Excel that has since been patched. If your computer has not been patched with Office XP Service Pack 3, you will receive this particular runtime 13 error when clicking a macro or a menu function based on a macro.
Runtime Error 13 and Visual Basic
Runtime error 13 (type mismatch) errors are not limited strictly to the Excel 2002 macro example above. They can occur within programs created with Visual Basic. When the underlying code contains values in the variable or property fields that do not match, the runtime error 13 message appears. These errors are usually related to the programming, not necessarily a problem with your computer’s configuration.
How to Fix Runtime Error 13
Since most of us are not programmers, you might think that there’s not much you can do about runtime error 13. However, this assumption is wrong. While the program may generate a runtime error 13 error when it can’t find a required file or variable, the reason could be because of a software bug or it could be because of a bad installation or file corruption. In addition, developers are constantly fixing software bugs, so a fix may be available.
In the Excel 2002 example above, a fix is indeed available: the Office XP Service Pack 3. Use this as inspiration and check for updates on any software that is generating runtime error 13 errors. If the developer has discovered the problem and repaired it, the fix will be included in a hot fix, update, or service pack. Once installed, your problem should disappear.
If the software has a repair tool, use it to repair the program. For example, Microsoft Office comes with a repair tool called Detect and Repair. This tool was later renamed the Microsoft Office Diagnostics Tool in Office 2007. Repair tools typically scan the program in search of lost or damaged program files and then replace those with fresh copies from the installation disc. If a repair tool is not available, try reinstalling the software.
Computer viruses and malware have been known to interfere with and modify Visual Basic files. These modifications can lead to runtime error 13 as well as other general errors. Update your antivirus and antispyware programs and run a full system scan to make sure that nothing malicious has corrupted your program.
Runtime Error Types
How to Fix Runtime Errors