p.s. I want to be able to keep the return code from the pre-cleanup, of course. So the exit code should not reflect the success of doing cleanup.
Some refs ;
1.[] ; ; ; ; ; X.SmartBear Search Results ; ;
http://smartbear.com/search-results/#search/cleanup/category/All/product/TestComplete2.[] ; ; ; ; ; X.Help with stopping a Project or Project Suite and running a cleanup routine ; ;
http://smartbear.com/forums/f74/fp192/t85777/help-with-stopping-a-project-or-project-suite-a/3.[] ; write a little script/keyword test to go back and delete the records you've created.
; ; ; ; X.How to clean up DB record created during test run ; ;
http://smartbear.com/forums/f81/t97786/how-to-clean-up-db-record-created-during-test-r/?utm_source=site-search&utm_medium=search-results&utm_campaign=site-search-c4.[] ; ; ; ; ; X.Handling Unexpected Exceptions ; ;
http://smartbear.com/forums/f74/t51485/handling-unexpected-exceptions/?utm_source=site-search&utm_medium=search-results&utm_campaign=site-search-ccan run your tested applications in
Debug mode, or run it using methods of the
DbgServices object, e.g.
DbgServices.LaunchApplication or
DbgServices.LaunchTestedApplication. In both cases, TestComplete will act as a debugger for your application and every time an exception occurs, it will automatically post an error message along with the call stack data to the test log.
5.[] ; ; ; ; ; X.Tracing Events and Exceptions With Debug Services ; ;
http://support.smartbear.com/viewarticle/55211/