Minimum Requirements for VBA coding and testing

[Anonymous]

I have a need to modify VBA 6 code to VBA 7.1 (AutoCAD 2010 to 2015 upgrade). I don't currently have AutoCAD and don't need to create/modify drawings, I've got DWG files (2D) and a dvb file(s). What are the product(s) I need to modify and test the VBA code (via VBA Enabler/VBAIDE) and later convert it to .NET? Will the LT versions work? The script is pretty straight forward, reading text from the DWG files and dumping it into Excel.

[Ed__Jobe]

VBA requires a host program to run in. LT does not support VBA, so the minimum you would need is AutoCAD. AutoCAD stores its compiled code in a dwg or dvb file, so you have to have a program that can open these files, i.e. AutoCAD. Once you open it in the vbaide, you could export the uncompiled code or copy/paste it. but you still need AutoCAD at least once for that. I know that's not what you wanted to hear, sorry.

[norman.yuan · Accepted solution]

---

@Anonymous wrote:
... I don't currently have AutoCAD ....

---

Well, you must have AutoCAD installed in order to do AutoCAD VBA. Period.

Also, moving VBA6.x (32-bit) code to VBA7.x could be a rocky path to go through, if you use 64-bit AutoCAD (thus 64-bit VBA, since AutoCAD2014). Depending on the your existing VBA code, you may not be able to find some equivalent components in 64-bit VBA. Therefore, this route of

32-bit VBA 6.x code -> 64-bit VBA 7.x code -> .NET API code

is a bad choice in most cases, unless your VBA6.0 are fairly simple, as your description sounds, IMO. You'd be better off directly looking at porting VBA code to .NET API code (you still need AutoCAD installed).

In either case, AutoCAD LT cannot be used.

[Anonymous]

Thx for the quick Replies. Hoping for a cheaper answer but was secretly expecting this one. Thanks for the info too. I'll consider the .NET move now as well or prepare for it if its necessary.