During testing your screen navigation will most likely break. There are many reasons that this can happen, among them:
| 1. | An unforeseen error on a screen prevents the ENTER or function key to advance to the expected screen |
| 2. | Due to the data behind a screen, instead of advancing to the expected screen, a new screen is displayed. |
| 3. | Due to the data behind a screen, the expected screen is skipped and a screen further-on in the normal sequence is displayed. |
Regardless of the symptom or the cause, the trace is the first place you can go to for diagnosis of this type of problem. Tracing navigation errors is a far faster method of debugging than using a step-trace debugger, such as that found in Microsoft Interdev or Visual Studio.NET.
Steps to Debug Navigation Errors:
| 1. | If using the Inventu Viewer+ COM or .NET components, consider using the HostConnection.LogText method to insert logging messages where your code is failing, to assist in locating the error in the trace. |
| 2. | If using any Screen Definition files, set Debug="Yes" in your definition file(s) in order to insert Screen Recognition analysis into your trace. |
| 3. | Reproduce the error with tracing on |
| 4. | Open the Trace Viewer and set the filters so that Emulation and COM/HLLAPI are checked, then Refresh the view |
| 5. | Scroll through the screens until you find where the navigation fails--note that sometimes you can also use the Control-F to find text faster than scrolling, particularly if you added LogText messages in step 1. |
| 6. | At this point, you should be able to identify the problem, and have the screens involved (with text locations) available to resolve the issue. |
