This issue is reducing me to tears.
When i attempt to change any value of any dimension style, i am no longer given the 'Ok' option to finish and close the dialogue box. Instead i get an error code and cad goes **** up.
Has anyone else had this problem? I recall that it arose when using civil 3D 2013 (which i've since uninstalled) and has continued into AutoCAD 2012 (installed post civil 3D 2013 uninstall).
Any help would be appreciated.
>> Instead i get an error code
What error message do you get? Can you make a screenshot of this message + the dialog with the missing OK-button?
The common questions to crashes:
- alfred -
Thank you for your reply.
I've discovered that unistalling the VBA enabler has done the trick.
thank you for your feedback!
- alfred -
I'm having this same problem with all dwgs (crashes on DIMSTYLE edits) prior to uninstalling VBA_Enabler. I could no longer modify dimstyles. Also "** Undefined shape <different numbers>" hundreds of times, fonts wouldn't work period. AutoCAD 2012 has never worked well on this computer (i7 3770, 16Gb RAM, tried 2 different video cards - formerly Quadro 600, currently FirePro W7000, which does not have certified ACAD drivers, but works great with Inventor and PDMS on 3 monitors).
And when I edit text, it disappears. When I finish editing it, it sometimes comes back, but when it doesn't, even undo won't get it back.
I don't know what's changed that would cause this now, unless it's a virus. We use ESET NOD32 Antivirus 4 (Business Edition). I have VBA code that I really need regularly.
I had so many problems with ACAD Mechanical 2012 that I resorted to using ACAD 2012, but both have these current problems with VBA Enabler. It's hard to believe that a company like Autodesk would settle for quality like this. AutoCAD 12 and 14 always worked much better. Could be they're just chasing dollars.
So my question is, can I use VBA, and still annotate in AutoCAD?
short answer? evidently that would be a 'no'.
VBA is a dead horse, & and has been fior a few years now. Even when it does run, it will slow down the machine drastically. Anything important you are running that is coded in VBA needs to be re-written using a working language that's still supported. creating a dotNet .DLL, LISP are options, or you could look into OpenDCL. Lots of choices, but they all require dumping VBA and using something else.