Screen Definition files can be tricky to implement accurately, particularly as you add additional screens; a prior screen definition may be "stealing" the recognition so that your screen is not recognized correctly.
Other problems can result from the presence of null characters or attribute bytes that are mixed with text in your Recognize tag criteria.
The best way to diagnose recognition issues is with the trace and the use of the debug="yes" setting in the top-level (FlyConnector) tag in your definition file(s).
To diagnose recognition problems:
| 1. | Set Debug="Yes" in your definition file(s) in order to insert Screen Recognition analysis into your trace. |
| 2. | Reproduce the error with tracing on |
| 3. | Open the Trace Viewer and set the filters so that Emulation and COM/HLLAPI are checked, then Refresh the view |
| 4. | Scroll through the screens until you find where the recognition fails--note that sometimes you can also use the Control-F to find text faster than scrolling. |
| 5. | Analyse the recognition failure using the special trace entry. A complete section on recognition trace entry analysis is provided in the Screen Definitions help at |
