Hi to you both and thanks for taking the time to respond to my question.
I've found the root cause of this issue - there seems to be an issue with the way Windows .bat files resolve the %PROGRAMFILES% Environment Variable when called from another application that is x86 rather than x64 (in my particular environment - virtual, connected with rdp etc etc).
I could isolate the problem by testing with another scripting solution that had a x86 and a x64 version. Specifically:
- if a .bat is called from x86 .exe, then the .bat resolves %PROGRAMFILES% as C:\Program Files (x86)
- if a .bat is called from x64 .exe, then the .bat resolves %PROGRAMFILES% as C:\Program Files - correctly in this case.
Just running the .bat makes the variable resolve correctly to C:\Program Files.
So from this I believe the issue is not TestComplete, just Windows in this particular environment :).
