Hidden Compiler Error

You have to give us more information about that error. Looks like you are using modules in your project? Did enable “Lock VBA project” in XLS Padlock’s VBA security page?
 
We changed the compiler options to build both 32 and 64 bit version (in one exe) for one of our users who is using excel 2016 x64 and they received this error when trying to open the compiled version. What do you mean by “…you are using modules in your project”?

Yes we always “Lock VBA project” in XLS Padlock’s VBA security page" and have hadno issues until someone tried to run on excel 2016 x64.

Thanks
 
The “Lock VBA project” option is certainly the culprit. We meant VBA modules, in your VBA project.
Your end user is getting an error in your VBA project and, since the latter is locked, you get the compile error in hidden module.
Did you test your original workbook with Excel 64-bit?
 
No. We had no request for it. And since the newer XLSPadlock supported both the 32 and 64 bit version we assumed that if there were no problems with anything that would be the case for the 64 bit version. So are you saying that our vba modules in the 32 bit version possibly will not work in the 32 bit version of excel?

2485d26919316b1d80aa60f5ca8e2cb5bc0275fe.jpg


fee8f01ce2acedefa01020ac274029c62e0a16f0.jpg
 
Last edited:
FTSC-PB said:
No. We had no request for it. And since the newer XLSPadlock supported both the 32 and 64 bit version we assumed that if there were no problems with anything that would be the case for the 64 bit version. So are you saying that our vba modules in the 32 bit version possibly will not work in the 32 bit version of excel?
Click to expand...
Came also across in a setup file…if Windows 10 make sure the installation is done with FULL admin rights …right click install as administrator
 
You must log in or register to reply here.
Back
Top