Thank you for this information. Adding "call" fixed my problem.<br><br>-Marc<br><br><br><div class="gmail_quote">On Fri, Jul 31, 2009 at 11:21 AM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Fri, Jul 31, 2009 at 11:14:39AM -0400, David Cole wrote:<br>
> This is not a VS specific problem, but rather how Windows batch files behave<br>
> in general.<br>
><br>
> If an executable or batch file returns an error exit status, but the "call"<br>
> keyword is not used in the calling batch file, then the calling batch file<br>
> exits without executing the remainder of the script. Using the call keyword<br>
> prevents that behavior and makes it work like you'd expect.<br>
<br>
</div>I have seen this behavior even when the batch file exits normally,<br>
without error condition. This is in VS2005 if it matters.<br>
<font color="#888888"><br>
tyler<br>
</font></blockquote></div><br>