14. Troubleshooting

Problems during design
Problems during generation or compilation
Problems when running the program
Getting Help

Problems during design

If you encounter problems while designing a Wizard screen or report:

• Get the technical documentation for the screen you are working on (see the Documentation menu from the Wizard screen generator menu).
• If an error message is being displayed, write it down. If the error message goes by too fast to read, you can get to the Wizard Screen Generator from TCL by typing FS. This can make it possible to read the error message.

Problems during generation or compilation

• Check the source code. It is in the W2 file unless you have changed the Program File Name with the EG Command. If your Wizard program is called EORDERS, you can examine it by typing ED W2 W.EORDERS.
• Print out the technical documentation for the screen. You can use this to check your code segments.
• If an error message is being displayed, write it down. If the error message goes by too fast to read, try typing TRAP at the menu before you generate or run the screen.

Note. When Wizard generates a Screen or Report program, it reads the Program Definition from the WVD file, and it creates a number of items. For example, if the Program Definition is called ABC, Wizard generates:

1. In the MD file, a proc called ABC which executes.
2. In the WPL file, a proc called ABC which executes.
3. In the MD file, a catalogue pointer called W.ABC which executes.
4. In the W2 file, the PICK-BASIC source code called W.ABC.
5. In the WIZHELP file, documentation (and help) items.

The files for 4 and 5 may be changed within the Wizard Screen Generator by using the EG Command.

Problems when running the program

• If an error message is being displayed, write it down. If the error message goes by too fast to read it, you can run the program from TCL rather than from a menu. This can make it possible to read the message.
• If the program aborts and displays an asterisk (*), type ? to see if the Object Verifies. If it does not, you have a Group Format Error (GFE) in the object code. Try generating the program again. (A GFE is a system error unrelated to Wizard, but remember that it may well be quite serious and should be investigated further.)
• If the program aborts and displays an asterisk (*), and does not display an error message, edit the Wizard proc in WPL and delete the error message Suppress option. For example, if your Wizard program is called EORDERS, type ED WPL EORDERS. Then find the line that ends with (S) and type R/(S)//. Run your program again to see if the error message is now displayed.

  The (S) option is used to suppress "divide by zero" messages so you may need to put it back.

• If you have specified a Lookup for a file, and the Lookup command (=) is not able to find the data, it may be because the data was entered before the Lookup on the file was specified (or entered without a Wizard Screen.) The Lookup command (=) will be able to find the "previously entered data" if you re-build the Lookup, this can be done from within the WAltAcc Screen.

Getting Help

Should you require further support, you can contact General Automation (Australia). If you are having problems with a specific program, we suggest you compress and email the WVD definition of the program to us, together with a detailed description of the problem, at wizard@pickproducts.com.au.

Should you need to contact us other than via email, you can find us at: