B. Defining Function and Control Keys : Restrictions and Limitations (Windows Environment) : Troubleshooting Checklist (Windows)
Share this page                  
Troubleshooting Checklist (Windows)
When troubleshooting your function and control key definitions, consider the following:
1. Have you checked the contents of the map error files in the working directory (ingkey.err or app_ingkey.err)?
The error messages written to this file indicate map file problems. For example, if the same key is referenced twice, the warning error message is written to this file. If this file is empty, an error occurred before the map file was parsed, and an error message was sent to your screen.
For example, no forms statements can be executed prior to starting the FRS. If a set mapfile statement preceded ## forms or exec frs forms in the embedded query language program, the error message is written to the screen.
2. Have any of the key map file path names become invalid?
For example, if the file system was moved to a new device, the file pathnames referred to by INGRES_KEYS or set mapfile are now invalid or perhaps file permissions were changed and the FRS cannot open the map files.
3. Are lower‑level key definitions showing through on the user's menu line?
This is the result of the key map merging by the FRS. This most often occurs when you forget to remap or turn off an intended key in the application map file or do not realize that INGRES_KEYS is also pointing to a map file.