Compile Error in Hidden Module

[jfalkowski]

So I have been plagued with an issue here lately as IT keeps updating things.  The last few workstations that have been configured have an issue with loswitch not working... yeah in know, its an old LISP and there are 100 ways to skin a cat but this is what we use and want to keep using.

The file is a visual basic coding that switches layer states when you switch layout tabs for those not aware.  I have a feeling it has to do with the Office 365 we are now running and its compatability with an older VBA language.  Some system specs:

All workstations are running:

Windows 10 Pro 64bit

Office 365

Civil 3D 2015 with all service packs, etc.

VBA Enabler

For some reason all of the other workstations are fine except one user and now me...just scored a new PC.  The error message is attached.

Any suggestions.  When the first user had the issue we tried a few things.  We tried 32 bit office, repairs, reinstalls.  Even wiping the unit clean and starting from scratch. 

I've tried this: http://forums.augi.com/showthread.php?141951-Microsoft-Visual-Basic-Compile-error-in-hidden-module-T...

Still not getting anywhere.  Does the inventor fix for VBA7 have anything to do with it??

Let me know, thanks!

Jon

[t_castl]

Hi @jfalkowski,

The error is raised when a compilation error exists in the VBA code inside a protected (hidden) module. The specific compilation error is not exposed because the module is protected.

To avoid this behaviour you can test one of the following options.

• If you have access to the VBA code in the document or project, unprotect the module, and then run the code again to view the specific error.
• If you do not have access to the VBA code in the document, then contact the document author to have the code in the hidden module updated.

As an possible alternative we suggest consider to migrate the VBA code to VB.NET.

For more information see the link below.
DevTV: AutoCAD VBA to .NET Migration Basics

Regards,

[jfalkowski]

Thank you for the response but I don't believe there is an error in the code.  We have been using the same file referenced on the server for a long time.  Several other computers are referencing the same file to date with no issues.  It's only on these fresh machines running the same software as all the existing machines.  The only difference is these were built from scratch and the other have all be upgraded.  From W7 to W10...and from Office 10/13 to 365.  These new units are not upgraded, just getting fresh installs of everything.

Jon

[jfalkowski]

Found the fix a while back...for anyone having the same issue.  I moved the file from a server located "LISP" folder to the server located "Support" folder and that's all it took.  Weird.

[votuananhvungtau]

I also got the same error VBA macros are usually working in some PCs in my co-workers, but not in mine