Is it possable to use VBA w 64 bit AutoCAD 2013.

[muck]

I have been trying to use my VBA routes with 64bit AutoCAD 2013 without any luck.

Seems like there is one problem after another so I would like to discusses this.

First of all is it possible the get VBA routes to work with AutoCAD 2013 64 bit.

 

One thing I don't know what references should be checked under tools-references because

there is so many of them.

 

At this point it appears that this is a end to my AutoCAD programming unless it can get an

handle on it.

 

Thank you,

[abraxus]

you shouldnt need to add any references unless you are trying to do something external, like sync your code with excel

 

perhaps if you gave an example of the types of problems you are having someone might have some ideas for you

[dbroada]

you do need to change references, check out this thread...

 

http://www.cadtutor.net/forum/showthread.php?79382-VBA-object-problems

[Tyke]

Don't give up Muck, all of your VBA routines should work on 2013, it uses exactly the same VBA Engine as previous Versions. But AutoCAD 2014 uses a different VBA Engine and your code may not work there. I have managed to get all my existing VBA to run on the VB7.1 in AutoCAD 2014, some of it needed tweaking a bit and some of the VB6 controls had to be replaced.

 

@ abraxus, references are sometimes an issue as AutoCAD can Change the AutoCAD type library reference which will prevent the VBA routines working on some Versions. The tip here is to look for MISSING refences and remove the tick to get them working again.

[abraxus]

interesting, tyke, i am not using Autocad 2014 yet, but it is good know that upgrading would cause some issues

 

is it just a matter of changing some references? or rewriting the code to match the new type library?

[dbroada]

I know tyke says you need new references for 2014, I needed to change the references when we changed to 64bit 2013, bbut no code re-writes.

[Tyke]

Dave is basically correct, but there are things like the progress bar that are no longer available in VB7.1, but I have been using one I developed myself so that is not a problem for me. Another control that is missing is the Common Dialog,but this is only a problem if you use a common dialog to open or save files and that is something my macros do a lot. You must then revert to using the Windows API or implementing a bitof Visual Lisp with the Send Command. I have also heard that the SHELL command does not work in VB7.1, But I haven't tested that yet.

 

It will be interesting to see how Autodesk will respond and if they will make new 64-bit controls. They have been pushing everybody towards Visual Studio and that is, according to Dev Tech, still their philosophy but they have also recntly intimated VBA is here to stay.

[abraxus]

there's a progress bar control??? lol - always just make my own... maybe i will look into that - does it make large iterations faster?

[Tyke]

there's a progress bar control??? lol - always just make my own... maybe i will look into that - does it make large iterations faster?

 

Nope, every progress bar has an overhead and will slow things down a bit, some more than others. They generally just keep the user amused whilst he's waiting

[abraxus]

i wouldnt use the term "amused"

 

i would say that a progress bar helps the user know that things are progressing, and that the program hasnt frozen up - and DOEVENTS helps them continue to do other things on their computer while the long loop is iterating, even tho it may have some overhead

 

there is a good way to slim it down tho

 

for i = 1 to 1000000

[process code goes here]

'progress bar code
if cint(i/100) = (i/100) then
 [update progress bar]
 doevents
end if

next