This is Automation object model code. This code can by executed only directly in a vbscript (executing the .vbs file manually), it should not by launched on UFT or executed from a function library called from UFT, since the purpose of this code is create the instance of UFT and control it by the code.
I understand it is AOM Code. Since it worked for QTP 11, I was hoping it will work for UFT 12. Do you think using this code in UFT 12 is creating a deadlock situation?
It is something I would have preferred not to use but I used as a work around for a different issue we ran into. We have a framework that involves calling nested library files i.e. first file loads the second file, second file loads third. To stop the test on error, we used 'ExitTest'. When 'ExitTest' is executed in the third library file, the test does not stop. Execution continues uninterrupted. 'ExitTest' works well when executed in the first and second library file.
I saw some references on googlign for this issue but I haven't seen a fix.