See http://www.serverobjects.com/products.htm<BR><BR>Two free components there. <BR><BR>ASPExec lets you start applications (you can do the same thing with WSH though)<BR><BR>AspProc gives you a list of running processes and lets you kill them.
I take it your refering to stoping the code as opposed to causing an error?<BR><BR>If so you use Response.End it will stop the code from being executed. If you need to stop and start code based on a varying condition your best to either use case, or if statements depending if you know what the variables are.<BR><BR>You could do something like this with IF statments:<BR><BR><%<BR>'Recordset declared<BR>Dim RS<BR>'Standard ASP Select statement here<BR>If RS.EOF = True then<BR>Response.Write "NO RECORDS"<BR>Response.End<BR>Else<BR>'Rest of your code<BR>End If<BR>%><BR><BR>Or if you don't want to response.write everything you could do this:<BR><BR><% If RS.EOF = True then %><BR><% Response.End %><BR><% Else %><BR>....rest of asp and or html code here<BR><% End if %><BR><BR>Hope this helps<BR><BR>James<BR><BR><BR>
You can start an application with Windows Scripting Host. <BR>That is a component BUT it is one you already have.<BR><BR>An example of using WSH to run a command can be found here:<BR>http://www.4guysfromrolla.com/webtech/102998-1.shtml<BR><BR>The example is of running a .bat file, but just a easily you could run an exe.<BR><BR>As far as killing an application... Don't think so.. There **might** be a way of doing it with WSH, but I have not seen any examples.