Strange error today in autocad

[slphantom]

our company has been getting this message this morning (see attached pic). it seems to do it when the dwg autosaves.

our computers are all win 7 64bit running plain 2012 autocad. I am wondering if this has something to do with windows 7 update we all got last night?

thanks in advance.

[Alfred.NESWADBA]

Hi,

are you running any modules in VBA? Does this error also exist if you don't load your DVB-file?

- alfred -

[slphantom]

yes we have some vba programs loaded when autocad starts up.

[Alfred.NESWADBA]

Hi,

>> yes we have some vba programs loaded when autocad starts up.

Do you get the error if you don't load the DVB's?

If you get these errors only during autosave, do you have the option to modify the DVB, at least under options that it stops at  every error? So you get into the debug-mode and we can see the code-line where it fails.

It would be also interesting what references are activated in your project ... can you list them here?

- alfred -

[TerryDotson · Accepted solution]

I am wondering if this has something to do with windows 7 update we all got last night?

Yes, it appears Windows Updates on 4/11 have (to say the least) negatively affected AutoCADs VBA on WinVista & Win7.  We began receiving similar reports from users of our OLD versions containing VBA yesterday.   In our testing VBA based code still works fine on WinXP, but fails with a subtle error (like yours) or worse causes fatal errors leading to AutoCAD closing.

We saw the writing on the wall in early 2008 and completely stopped using VBA.  All of our software since then uses the Managed .NET API (pure .NET, not COM) which contains no VBA.

[Alfred.NESWADBA]

Hi,

>> In our testing VBA based code still works fine on WinXP, but fails with a subtle error

Can you show sime lines that will fail?

I have VBA installed (but just as in case of "need to write a fast tool for one job", so not running an indeed no events), but for now I don't see any problem.

- alfred -

[slphantom]

I took the only vba program i had in my appload briefcase and removed it. i have not see the error since.

thanks.