If you have been clinging to a library of VBA macros written for AutoCAD 2010 or 2012, upgrading to AutoCAD 2013 likely gave you a headache. When Autodesk made the jump to a true 64-bit application architecture with AutoCAD 2013, many users discovered that their VBA routines simply stopped working.
You cannot install the VBA module while AutoCAD is running. Ensure the application is completely shut down. autocad 2013 vba module 64-bit
The AutoCAD 2013 VBA module is stable. If you have a massive legacy codebase, it is worth installing. However, note that Autodesk has not significantly updated VBA since 2013. If you have been clinging to a library
While the VBA module allows the code to run , you may need to modify your code if it interacts with the Windows API or uses Declare statements. Ensure the application is completely shut down
Navigate to the Autodesk Subscription Center or the official Autodesk Knowledge Network. Look for: AutoCAD_2013_VBA_Module_64-bit.exe
Declare PtrSafe Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtr Use conditional compilation to maintain a single codebase for both bit-versions: