The solution to your problem lies in the architecture of the project (the MDS file) and other internal codings within the project. The specifics, in a general list are:
1) Go to Tools | Current Project Properties | Playback and verify the settings for Stop on Error and Stop on Exception. Having these two flags checked, as soon as an error or Exception is logged, will halt the run of that MDS project file. This may or may not be desirable but it is something to consider
2) In the Test Items in the project, there are additional "Stop on Exception" and "Stop on Error" flags that can be set per test item in order to control the flow of the project.
3) The OnLogError event handler can be used to add additional fine-tuning to this workflow control by executing code to recover from errors, stop the current test, etc.
4) Utilizing Try/Catch/Finally code within the test code itself will help to better recover from errors and make sure that tests don't continue to attempt to run after critical errors occur.
All this is done within the specific projects and/or tests and is not controlled by the commandline.
