Forum Discussion
Vicky,
I'd suggest typing the element name in upper case (i.e. INPUT instead of input) and the attribute name in the way it is specified in the page sources. These are requirements mentioned in the EvaluateXPath method description.
I checked your code and failed to reproduce the problem. I tried TestComplete 8.60 with IE8 and FF7, and these versions of the browsers are later than those you used. However, I suppose, everything should work fine in earlier versions too. So, if you address the appropriate browser process (the process index may change depending on the tab) and if the page contains the INPUT element with attribute id="flightSearchForm.tripType.oneWay", this code should be able to find the element. Could you please check if the element exists on the page?
Also, what kind of pages are you testing? I ask about this, because the element may be generated dynamically and you need to pause your test a little until the element appears on the page and TC updates the hierarchy of test objects. To pause the script, you can use the aqUtils.Delay method. To command TestComplete to update the object hierarchy, use Page(...).Refresh.