VbaCompiler

  • VBA Compiler
    • Features by licenses
    • How to compile
    • Compiler options
    • Backend C Compiler
    • Excel VBA copy protection
    • Create trial / demo version
    • Protect Excel workbook template
    • Runtime API Functions
    • Custom Run-Time Messages
    • VBA command line compilation
    • Compile Time Troubleshooting
    • Workbook Run-Time Troubleshooting
    • Distribute Workbook
    • EULA
    • Privacy Policy
  • Best way to protect VBA code
  • VBA Speed Up
    • VBA Benchmarks
    • Optimize VBA code
  • Frequent Questions
  • Download
  • Order
  • Contact us

Run-Time Troubleshooting Procedure

 

Workbook run-time troubleshooting can help you find and resolve common issues that may stop a compiled application from running correctly. If the workbook with VBA code has been successfully compiled but it does not run, you should check the following reasons in the computer environment that are preventing it from opening. Some of these reasons may also cause incorrect run-time behavior and should be resolved through the described solutions.

 

Verify Whether Windows Operating System Has Pending Updates

Please verify whether your Windows operating system has pending updates. If so, please ensure that you complete the Windows OS update first then reboot your computer.

 

Verify Whether MS Office has latest updates 

Please make sure that you have the latest service packs and updates for your version of MS Office.

 

Workbook Run-time Antivirus Troubleshooting

Antivirus software may interfere with the normal behavior of the compilation process as well as the final result. To ensure that our compiler and your application is working correctly, please temporarily disable your antivirus software. Afterwards, you can then open your compiled workbook with VBA code. If the workbook started successfully after disabling the antivirus, then the issue is a false positive detection from the antivirus. To reduce antivirus false positive detections, you must input the folder where your protected workbook is located into the antivirus exception list. We encourage to apply a digital signature for the compiled workbook to reduce antivirus false positive detections.

 

Troubleshoot that You Have Appropriate Security Permissions for the Run-time Workbook

You may have insufficient security permissions to save files into or open them from certain folders on your computer.

Please copy your protected workbook to the “My Documents” folder (or any of its sub-folders) on your computer. After doing so, try to open it again.

You can also try running the compiled workbook as an administrator by select the compiled workbook in the Windows Explorer, right-clicking the file and then clicking on “Run as Administrator”. This will elevate your current user permissions and verify whether the lack of security permissions is the reason of the problem.

 

Verify preinstalled third-party Excel Add-ins

Some third-party Excel add-ins may interfere with the normal behavior of a compiled workbook. In certain cases they may even block the application’s functionality completely. We recommend temporarily removing such Excel add-ins. This will stop the add-ins from interfering with the workbook’s functionality.

 

Verify that all required VBA ActiveX components are installed

If your workbook uses ActiveX components in VBA code, this section is of note. The absence of these components on the client computer may lead to the incorrect behavior of the compiled workbook. Make sure that all ActiveX components are present in the VBA Editor main menu > Tools > References on the computer where the problem occurs.

workbook run-time troubleshooting through vba editor, tools, references

 

If all of the previous troubleshooting approaches  don’t fix the problem

In this case it is possible that the reason is an error in VbaCompiler itself. In order to be able to fix the error we need to reproduce the situation on our side. To do this successfully we need your help!

 

Please provide us with the following information:

  • A workbook example with the uncompiled VBA code which leads to problem.
  • A screenshot of the compilation options or the VbaCompiler for Excel project file (.vcprj file) that you use for compilation.
  • A screenshot of the MS Excel About box from the computer where the problem appears.

 

Send this information to support@vbacompiler.com.
Please note that we do not need your original workbook. You can modify the example in any way that you want, but the main requirements are as follows: the VBA code must not contain any of the VBA syntax errors and the error must still be present when VbaCompiler compiles the workbook VBA code that you are sending to us.

 

See also:

How to distribute protected worbook

How to apply digital signature for protected workbook or/and VBA project

  • VBA Compiler
    • Features by licenses
    • How to compile
    • Compiler options
    • Backend C Compiler
    • Excel VBA copy protection
    • Create trial / demo version
    • Protect Excel workbook template
    • Runtime API Functions
    • Custom Run-Time Messages
    • VBA command line compilation
    • Compile Time Troubleshooting
    • Workbook Run-Time Troubleshooting
    • Distribute Workbook
    • EULA
    • Privacy Policy
  • Best way to protect VBA code
  • VBA Speed Up
    • VBA Benchmarks
    • Optimize VBA code
  • Frequent Questions
  • Download
  • Order
  • Contact us
Copyright 2005-2025 © DoneEx LLC. All Rights Reserved.