Comments on: Port Your ObjectARX Code to 64 Bit

By: skatterbrainz

skatterbrainz — Fri, 12 Mar 2010 16:47:01 +0000

I find it humorous how intense the Autodesk marketing was to push developers away from LISP to VBA, saying it was "the future". Then they dump VBA after years of customer time spent doing just that. Only to realize (quietly, of course) LISP is still sitting there, working fine as always. Now they're starting the same bs marketing with .NET. Anyone remember the story of the boy who cried wolf?

By: Owen Wengerd

Owen Wengerd — Fri, 12 Mar 2010 14:29:23 +0000

It's unfortunate that a respectable company like Eagle Point is leaving customers high and dry on the 64 bit architecture, but I suppose they felt that even a few hundred dollars is too much to invest in a dying product.

By: Owen Wengerd

Owen Wengerd — Fri, 12 Mar 2010 14:26:16 +0000

VBA still works in 2009 and 2010, but any application that requires interprocess communication between AutoCAD and VBA is much, much slower on 64 bit AutoCAD.

By: Chris Cowgill

Chris Cowgill — Fri, 12 Mar 2010 13:17:49 +0000

Owen, I have discussed this issue with you in the past, Eagle Point has refused to port their product to 64 bit, and now that they are closing the doors on their civil software for vanilla cad, I dont expect them to. Our office was forced to install 32 bit Windows, just because of this one program. I wish they would have taken you up on your offer to port their software, but for now, I just have to wait until Eagle Point goes away, then our office will switch to some other software that supports 64 bit.

By: Anonymous

Anonymous — Fri, 12 Mar 2010 11:58:11 +0000

I'm running 64-bit AutoCAD 2010 on XP SP3 64-bit and the VBA Enabler loads and runs just fine. Never had a problem installing it or with it running. Also, Autodesk didn't pull VBA out of the base installation setup until 2010. AutoCAD 2009 still installs it. Am I missing something?

By: Steve Johnson

Steve Johnson — Fri, 12 Mar 2010 06:10:41 +0000

I have a home-grown app that relies on a free 4th party 32-bit DLL that is extremely unlikely to ever be updated, regardless of any pressure I may attempt to apply. Does this count as a valid excuse?