Hi Matt,
Once you establish that you cannot avoid a dialog box from another program
with SendKey/SendCommand type processes, then the next step it to bypass the
dialog box and write your own code to perform the functions behind the
dialog box.
If the whole function behind the dialog box is too complex for you to code,
then ultimately you may be better off opening the box and allowing the user
to process it manually.
If you are totally insistent of using the dialog box, the next level of
complexity may be to drive mouse clicks at the relevant screen coordinates
of the items on the form.
--
Laurie Comerford
CADApps
www.cadapps.com.au
"matt_1ca" wrote in message
news:19101957.1109290375034.JavaMail.jive@jiveforum1.autodesk.com...
> Hello Laurie,
>
> Thank you for your reply.
>
> Your idea has given me a good start, out of the seven clicks on the dialog
boxes your technique allowed me to find a way to call two of those clicks
from the command line -- I still need to click five buttons though, and I am
not finding it possible from command line.
>
> Setting cmddia/filedia to zero has not gotten rid of the dialog box -- I
think they are like dialog boxes used by vbaman which are not disabled
despite cmddia/filedia settings of zero.
>
> Even though cmddia/filedia did not disable the dialog boxes that pop out
your idea made me look into the command line to see what commands are being
pumped in the command line that I was able to use to my advantage.
>
> Those other five buttons dont show any corresponding commands in the
command line, so I cannot call them the way I called the other two. One of
those five buttons for example activates a browser window to select files to
use as templates for spatial data extraction and repopulating AutoCAD based
on user's new SQL etc.
>
> Matt
