Sharing a screenshot would not be possible since my testcomplete is on a closed network computer. I click on the text box and press tab, nothing happens so Ill try pressing tab again, and still nothing happens. The test recognizes that I am pressing
"[Tab]" but it does the program does not act accordingly.
Another weird thing is once I stop recording and the application is still open, then the application no longer accepts tab inputs either. If I open the application without testcomplete then tabs work fine but somehow launching from testcomplete is stopping the tabbing functionality even after testcomplete has closed.
Well...
1) Are you doing script code or keyword tests?
2) Are you using the "Keys" method in your tests?
3) What OS are you using?
4) What component class is it?
5) How is the object mapped?
This is, basically, what we need to know before we can even start to troubleshoot. Generally speaking, the "tab" method works very well for many people so it has to be something unique to your environment/application/implementation.
1) I am creating this specific test using the record and playback so keyword test. Although I will say that I do plan on converting it to a script after it is made working correctly.
2) The operation in the keyword test is Keys yes. I am physically doing the exact same motions I do when it normally works just this time I have the TestComplete recorder open.
3)I am on Windows 7 64 bit.
4) I don't know. What is is a component class/ How do I find that out?
5) It is mapped by its winforms control name.
Out of curiousity... do you have a virus scanner of some sort running on that machine? It's possible that something may be intercepting TestComplete's hooks into the Keys method.
