If you use VBA inside of 32bit AutoCAD you will have noticed that it is around 1000x times slower when running the same VBA code inside of 64bit AutoCAD.
This is because AutoCAD 64bit ships with the 32bit VBA DLL in a separate out-of-process executable rather than loading the VBA DLL inside of AutoCAD itself. Therefore, a lot of marshaling is incurred communicating between the out-of-process VBA executable and 64bit AutoCAD.
Other issues you may be seeing: Run-time error ‘429’: ActiveX component can’t create object
Affected, all 64bit versions of (and variants of)
AutoCAD 2008 | AutoCAD 2009 | AutoCAD 2010
AutoCAD 2011 | AutoCAD 2012 | AutoCAD 2013
AutoCAD 2014 | AutoCAD 2015
AutoCAD 2016 | AutoCAD 2017
The best solution is to install 32bit AutoCAD on 64bit Windows, here are the affected versions along with their solution text…
There is an App built which specifically scans AutoCAD’s setup so that either the 1603 error is gone (fixed) or it does not affect the install… Check out the blogs on how to fix your AutoCAD’s 1603 error (if your version is not listed below use the search box at the top right of this page)
If you are getting Error 1935. An error occurred during the installation of assembly ‘Microsoft.VC80.OpenMP.type=”win32″.version=”8.0.50727.42″ when installing your AutoCAD 2008, try these steps to resolve it:
Delete all files (*.*) from your C:\Windows\System32\config\TxR folder