acadentity doesn't work

Hello,

I have many programs that use acadentity to get something from the
drawing, then set blockentity=acadentity etc.

Suddenly they are crashing. It says this is not allowed. if i change the
entity to object instead of acadentity then the set command gives type
mismatch.

thanks for any help with this

jm

 

Let's see some code...

 

okok here's the problem
only recently has this started to not work

Public Sub dcx()

Dim oEnt As AcadEntity
Dim v1 As Variant
Dim oblock As AcadBlockReference
Dim oAtt As AcadAttribute

ThisDrawing.Utility.GetEntity oEnt, v1
Set oblock = oEnt 'this is where it says "Object library feature not
supported"

End Sub

 

I'm on 2005 and that works okay for me. Make sure a block reference is
what's being selected.

 

To do that, use TypeOf in an If statement. See help for an example.

 

Hello,

Its not that the program crashes. It never gets a chance because as soon
as it loads the interpreter throws the error "Object library Feature not
supported".

I feel like that my playing around with Dot Net has messed up my other
programs.

I can define oEnt as an Object instead of an ACADentity but then i can't
Set that as a block for example because type mismatch.

thanks for lookin at it anyway

jm

 

You didn't say that before...Do you have any missing references?
Tools>References, You're using vba I assume?

 

no missing references but now i notice the programs work fine in 2005
the error only occurs in 2004

so i guess i will just uninstall the 2004

thanks!

 

You can't rund the *same* dvb in 2004 *and* 2005. The first time you run it
in 2005, it will compile for 2005 and then no longer work in 2004. Use
separate dvb's for each app.

 

aha! this is important...
i was beta-testing my office programs for 2005 and still using 2004 for
production

thanks ed

 

BTW, you also didn't say that before. Give as much info as you can when
trying to troubleshoot a problem.

 

Ed,

can you elaborate on this ? I remember once I had to modify a DVB made for
AutoCAD 2000 on AutoCAD 2004, and it worked like a charm when exceuted on
2000. I must add I did not use features available on 2004 that were not on
2000.

Gilles

 

AFAIK this is peculiar only to 2004 and 2005.