You can test the application at any time during development by choosing Go from the Applications Catalog frame or the Edit an Application frame, or from any frame.

The Go operation compiles all frames and source code files needed for the test into the database catalogs. For example, if frame A calls frame B, and frame B calls frame C, a test of A checks A, B, and C for recompilation, but a test of B only checks frames B and C.

To test a 3GL procedure that receives parameters from an ABF frame, select Go from the calling frame. Do not select Go from the 3GL procedure, because this has unpredictable results, suc as the 3GL procedure not working properly or your system returning an Access Violation.

If the application runs under a role, ABF prompts you for the role's password. For security reasons, the password is not displayed on your terminal screen as you type it in. ABF prompts for the password twice. Once you enter a password for an application, you are asked whether you want to use the same password again.

If there are no errors, Go then runs the application, prompting you for the frame to call first. If you select Go from a completed frame, ABF asks if it must start at this frame.

In contrast to the Go operation, you can use Compile to compile a single frame and correct any errors, but Compile does not run the frame. To run, your current frame and all non-4GL procedures must be error-free.

When you choose the Go operation, ABF cannot check the dates on libraries included by the linker options file. For the purposes of building an interpreter, ABF assumes that no modules in the linker file are updated during the current editing session. To link any modules that were updated during the current session, the user must exit from ABF, or go at least as far as the Edit an Application frame, and re-enter the application using the Edit or Go operation. This forces the updated modules to be linked.