** That command may not be invoked transparently **

[Anonymous]

sometimes when trying to execute an activex command from visual basic 6.0 to
autocad 2000 i get this message :
** That command may not be invoked transparently **
and executions halts.

does anybody know what does this mean and how to get around it?

[Anonymous]

It sounds like you are trying to call an AutoCAD command while another is
running.

--
Andy Cottrell
Applications Engineer
ExcelTech Computer Services
E-Mail: acottrell@exceltech.net

Dimitris Papadimitriou wrote in message
news:7vlbiu$jpr15@adesknews2.autodesk.com...
> sometimes when trying to execute an activex command from visual basic 6.0
to
> autocad 2000 i get this message :
> ** That command may not be invoked transparently **
> and executions halts.
>
> does anybody know what does this mean and how to get around it?
>
>

[Anonymous]

I had the same problem.
Couldn't really figure out why.
Probably has something to do with the state AutoCAD thinks it's in.

In my VBA code I send a couple of escapes to command line before trying
to interface with the drawing editor.
I haven't had the problem since.

Mark

>sometimes when trying to execute an activex command from visual basic
>6.0 to autocad 2000 i get this message :
> ** That command may not be invoked transparently **
>and executions halts.
>
>does anybody know what does this mean and how to get around it?
>
>

[Anonymous]

I have a Microsoft Intellimouse Explorer with the wheel (middle button)...
My code gives me this error message after double clicking the wheel to
execute a "'_.zoom _e"

** That command may not be invoked transparently **

How can I make sure A2002 is ready for me to interact with my code?

Rodney

[Anonymous]

Hello all,
I have found that I sometimes get an error when I try to interface with the
drawing editor from VBA. This error only happens following a middle-button
double-click zoom-extents.

For some reason zooming to extents using this method leaves the document in
a state that doesn't want to respond to VB. It's especially aggravating
because the error shows up at the AutoCAD command prompt and not in a VB
error dialog. It says "** That command may not be invoked transparently **".

I've been able to trap it by examining the "LASTPROMPT" variable.

I have been able to to work around this problem by putting [
ThisDrawing.SendCommand "Zoom 1x " ] in front of my Select call. This
happens even when the Select type isn't a call to SelectOnScreen.

My work-around is a bad hack. I've found it doesn't work in all cases.

Any alternatives?

[Anonymous]

This is a known problem (and one I'm way too familiar with).

The only workaround I've found, is like the one you use
except I use SendCommand("redraw ").

"Mark Johnston" wrote in message
news:E8F37CDD1B99A80EE3197EEC815C23F5@in.WebX.maYIadrTaRb...
> Hello all,
> I have found that I sometimes get an error when I try to interface with
the
> drawing editor from VBA. This error only happens following a middle-button
> double-click zoom-extents.
>
> For some reason zooming to extents using this method leaves the document
in
> a state that doesn't want to respond to VB. It's especially aggravating
> because the error shows up at the AutoCAD command prompt and not in a VB
> error dialog. It says "** That command may not be invoked transparently
**".
>
> I've been able to trap it by examining the "LASTPROMPT" variable.
>
> I have been able to to work around this problem by putting [
> ThisDrawing.SendCommand "Zoom 1x " ] in front of my Select call. This
> happens even when the Select type isn't a call to SelectOnScreen.
>
> My work-around is a bad hack. I've found it doesn't work in all cases.
>
> Any alternatives?
>
>
>
>