Hello Maeve,
Actually, the object recognition and script recording functionality of TestComplete is the same for all scripting languages. So, the problem you are having is not related to the scripting language you are using. Feel free to use JScript if you like it.
The scripts you posted are almost identical in the sense of functionality, but there is one line in the JScript version of the test that indicates a problem:
>>> frmOpenStudyOptionDialog = OCDSClient_OCDSStudyManager.wndWindowsForms10Window8app0129c866;
Mapped names like "wndWindowsForms10Window8app0129c866" can be given to a window of a .NET application when the application is not recognized as Open by TestComplete for some reason. Taking into account that the problem is not persistent, I would assume this is a timing problem - the tested application sometimes gets busy for a long time and TestComplete cannot initialize its .NET Open Applications engine for this application. If my assumption is correct, increasing the value of the "Open Applications | General | Method invoke timeout" setting of your project should solve the problem.
So, delete the "wndWindowsForms10Window8app0129c866" object from the Name Mapping tree and record your test anew.
If you face some problems with this, let me know.
