Progress
Results User’s Guide
for UNIX


Description of the Initial Build

When you first run Results against a database, you see the following message:

In this message, dbname is the name of the database you are using to start Results. If you are starting Results with more than one database, dbname is the name of the first database you specify.

The initial build creates a file called dbname.qc that contains the Results default settings (for example, file relationships, form interfaces for the query module, and output destinations.) Results cannot run without the query configuration (QC) file. Therefore, if you are running Results for the first time against a database or group of databases, you must perform the initial build to create this file.

The QC file is named for the first database connected, so remember the order of the databases when you start Results with more than one database. For example, if you perform an initial build on the databases dbname1 and dbname2 (in that order), the .qc file for these databases together is called dbname1.qc. If you start Results with dbname2 and dbname1 (in that order), you see a message that the dbname2.qc file was not found. If you start Results with only the dbname1 database, you see a message that dbname2 is needed but not connected. If you want to start with only dbname1 you must do the following:

NOTE: You can start Results with more databases than you used to build the .qc file. However, if you enter the Administration module and then exit, Results rewrites the .qc file. Then that QC file requires the additional databases when you start Results with it again.

If you want to start Results with database1 and another database, connect the other database first. For example, if you already have a database1.qc file, you can start Results with database3 and database1 (in that order). The QC file for the initial build for these databases is called database3.qc.

After you select Yes from the initial build prompt, you see this screen:

If you select AUTO, Results automatically creates query forms for each of the files in the connected database(s).

If you select SEMI, Results builds query forms for the files you select from a list. After you select the files, Results builds the default forms.

NOTE: For more information about the AUTO and SEMI options, see the "Default Forms" section in this chapter.

If you select MANUAL, you can define your own form for each query interface through a series of screen prompts. When you choose MANUAL, the Form Definitions for Query submenu appears. Follow the same process to define query forms when you choose MANUAL as you follow when you choose the Form Definitions for Query option from the Administration Main Menu. The "Form Definitions for Query" section in this chapter describes how to define and modify query forms.

Once you select an option, a status screen lists the names of the files as they load from the database into Results. The program names in this screen are created using the first eight characters of the filename. If a program is already used by another procedure, Results assigns the name qryxxxxx.p, where xxxxx represents a unique integer value.

Even when you define forms manually, Results automatically sets all other defaults, for example, file relations, printer settings, terminal colors, and permission. If your database contains many files that do not require query forms, the MANUAL option saves you time because you only build the query forms you need.

During the initial build, and during subsequent form definitions for the Query module, Results automatically places the procedure files, include files, and form definition (.f) files in the current working directory. You can later move them anywhere in the PROPATH. For more information about PROPATH, see the Progress Installation and Configuration Guide Version 9 for UNIX.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095