Defining Frames without Visual Queries
Vision generates Menu, Append, Browse, and Update frames that let you include a wide range of user operations and query specifications in your applications. In addition, you can increase the scope of your applications by including frames that access other Ingres tools.
For example, you can create a frame to display a report created with RBF or to run a query defined in QBF.
You also can include frames and procedures for which you write the code.
Because Vision does not generate the code for these frame types, they do not have visual queries. To use one of these frame types in an application you must:
• Create a new frame in the Application Flow Diagram (as described in
Creating Frames) specifying the appropriate frame type
• After you create the frame, define it to Vision; that is, provide information about its components:
– Forms
– Query object (such as a report or QBF JoinDef) or source code file
These components can exist before you create the frame or, in most cases, you can create them at the same time. All the components must reside in the same database as the Vision application in which you use them.
This chapter describes how to define frames and procedures that do not have visual queries. These include:
• QBF frames
• Report frames
• Graph frames
• User frames
• 4GL procedures
• 3GL procedures
• Database procedures
For a description of each of these frame and procedure types, see
Overview of Vision.
You cannot create child frames in the Application Flow Diagram for any of the frame types listed above. However, you can call other frames through the 4GL code for User frames and procedures (with certain exceptions, as described in this chapter). Frames called in this way do not appear in the Application Flow Diagram.
For information on how to use ABF to create frames and call them from your application, see
Using Vision or ABF in a Multi-Developer Environment.
Last modified date: 08/28/2024