Topic: error: no function definition: VLAX-GET-ACAD-OBJECT

[Chris]

Here is probably a new one for you.

I have AutoCAD 2010 32 and 64 bit, when I run my customizations, on the 64 bit version, everything loads properly.
If I attempt to run 32 bit, I get this message:

error: no function definition:
VLAX-GET-ACAD-OBJECT

Here is a portion of my code:

Code: [Select]


(vl-load-com)
(setq acadObject (vlax-get-acad-object))

Is there a separate arx file that AutoCAD should be loading that allows the visual lisp commands to function? Even in VLIDE, the function isnt blue, it shows as black.

I'm confused, any suggestions?

[Lee Mac]

I had this similar thing...

I just manually typed (vl-load-com) at the command line, and hit enter - then all was fine from then on. So I just chucked (vl-load-com) in my ACADDOC, but yes, when it first happened to me, I was stumped.

[Chris]

I did what you described and it still isnt working

[Lee Mac]

OK, that is weird then...

[Kerry]

... Even in VLIDE, the function isnt blue, it shows as black.

does it show as protected (blue) after you run the (vl-load-com) function ??

works for me in 2010

///kdub

[Chris]

no

[Kerry]

best guess then : you have a faulty install ..

[Chris]

I'm also getting some error that a library isnt being registered.  The error appears on my command line after acad.lsp is run, and before my acaddoc.lsp fires up.  Not really sure what isnt being registered, I ran my acad2010doc.lsp file manually and got no error messages, and still nothing worked.

on the faulty install:
I would guess that because half the dll files and such wernt copied to the directory, but I compared it to another installation and manually copied stuff over from the installation disk.  maybe it is a registry entry, because I have the identical files in all required folders as an installation that works properly.

[cadgene]

I have the same problem! it is driving me crazy. It works on a 32 bit PC but not on a 64 bit. I tried everything.

[Chris]

my solution, install 64 bit AutoCAD on 64 bit windows, the workaround that has been posted on the Internet, doesnt seem to work for 2010 and above.  (unless someone has come up with a new way of getting around it.)