Process Multiple Drawings via VBA

I've got a program that SHOULD perform multiple tasks to multiple drawings, however, when I run the program, all it does is open then save the drawing and then move on to open and save the next drawing.... It doesn't perform any of the tasks! Am I missing some magic keyword to make this happen or am I just experiencing a brain-freeze??

Thanks in advance!
  ~ Matt

 

This is code within the loop to open, process, and save...



 



For blah blah blah = 1 to blah blah blah



        ThisDrawing.Open dwg
        ThisDrawing.Activate



        ThisDrawing.SetVariable "filedia", 0
        ThisDrawing.SendCommand "change" & vbCr & "all" & vbCr & "" & vbCr & "p" & vbCr & "c" & vbCr & "bylayer" & vbCr _
                            & "lw" & vbCr & "bylayer" & vbCr & vbCr
        ThisDrawing.SendCommand "mslide" & vbCr
        ThisDrawing.SetVariable "filedia", 1
        ThisDrawing.Save





Next blah blah blah



 




--
Matt W



 



There are 3 kinds of people:
  Those who can count, and those who can't.

 

I notice you only have 1 vbCr after mslide... you need a second vbCr to
accept the default filename and execute the command.... if you're trying to
get the program to sit at the filename prompt to let you enter one, I don't
think SendCommand will allow that, because the code doesn't stop running...
there are simple tools you can use if you want to input the filenames
yourself.

Also, the "change" SendCommand *should* be replaced with a selection set and
calls to the .COLOR and .LINEWEIGHT properties, but I don't know that this
is contributing to your problems. If you get it working with this line in
it, good enough.... I would think that the larger your drawings get, the
more chance this line would have of causing problems, since it would take
longer and longer to process.

HTH,

James

 

Ok Robert (or anyone else) answer me this, The send command runs last in the
sub no mater where it falls at in the code.As to what I read somewhere. So
in BVC-CAD's example the "ThisDrawing.save" is executed then the
sendcommand(s), there by none of the changes are saved. Am I correct?

Murph

 

Yes. ;-)

--
R. Robert Bell, MCSE
www.AcadX.com


| Ok Robert (or anyone else) answer me this, The send command runs last in
the
| sub no mater where it falls at in the code.As to what I read somewhere. So
| in BVC-CAD's example the "ThisDrawing.save" is executed then the
| sendcommand(s), there by none of the changes are saved. Am I correct?
|
| Murph
|
|
|
| | > SendCommand is likely the problem. You could try a DoEvents after each
| > SendCommand, but I don't know if that will help. You could iterate thru
| the
| > drawing changing your properties, to avoid that SendCommand. There is
| > nothing in the object model for MSlide.
| >
| >
| > --
| > R. Robert Bell, MCSE
| > www.AcadX.com
| >
| >
| > | > | This is code within the loop to open, process, and save...
| > |
| > | For blah blah blah = 1 to blah blah blah
| > | ThisDrawing.Open dwg
| > | ThisDrawing.Activate
| > | ThisDrawing.SetVariable "filedia", 0
| > | ThisDrawing.SendCommand "change" & vbCr & "all" & vbCr & "" &
| vbCr
| > & "p" & vbCr & "c" & vbCr & "bylayer" & vbCr _
| > | & "lw" & vbCr & "bylayer" & vbCr & vbCr
| > | ThisDrawing.SendCommand "mslide" & vbCr
| > | ThisDrawing.SetVariable "filedia", 1
| > | ThisDrawing.Save
| > | Next blah blah blah
| > |
| > |
| > | --
| > | Matt W
| > |
| > | There are 3 kinds of people:
| > | Those who can count, and those who can't.
| >
| >
|
|

 

Thanks.
Murph

 

What I find is that the SendCommand runs first, and the changes *are* saved.
Maybe this is not guaranteed because it's not running synchronously, but on
my quick test drawing, things get changed first, then saved... not vice
versa.

James

 

SendCommand has the tendency to run asynchronously on various flavors of
AutoCAD. Personally, I've never run into trouble either, but many have.


--
R. Robert Bell, MCSE
www.AcadX.com


| What I find is that the SendCommand runs first, and the changes *are*
saved.
| Maybe this is not guaranteed because it's not running synchronously, but
on
| my quick test drawing, things get changed first, then saved... not vice
| versa.
|
| James
|
|
| > Yes. ;-)
| >
| > | there by none of the changes are saved. Am I correct?
| > |
|
|

 

Murph & Robert:

The DoEvents fixed the "glitch".
What was happening was exactly what Murph had described; the SendCommand
events were happening *after* the drawing was saved, therefore, not saving
anything.

Thanks for the input guys.

 

Your Welcome Matt even though Robert confirmed what I thought. Got to mark
this date on the calendar got a VBA question right.
<g>
Murph