Release 10.1A: OpenEdge Reporting:
Query/Results for Windows

> ## Preface

> This Preface contains the following sections:

> - Purpose

> - Audience

> - Organization

> - Using this manual

> - Typographical conventions

> - OpenEdge messages

> ### Purpose

> This guide introduces you to Progress ResultsŪ. Query/Results, more commonly referenced throughout this guide as Results, is an interactive, menu-driven tool that lets you query, report, and maintain information stored in Progress-supported databases.

> ### Audience

> This guide is an end-user manual that explains how to use the default Results application. If you purchased Results through a third-party application vendor, the vendor might have modified Results. These modifications might include adding or removing features, or even incorporating Results into another application. If you have a modified Results application, your vendor might modify the help system to reflect these changes or provide you with additional documentation.

> ### Organization

> Chapter 1 "Results Overview"

> Briefly describes the benefits of using Results, then explains basic database concepts.

> Chapter 2 "Results Basics"

> Explains how to start and stop Results and use the online help system.

> Chapter 3 "Query Basics"

> Explains how to use Results to query information in a database, then print and save your queries.

> Chapter 4 "Using Query Views"

> Explains how to use the browse, form report, label, and export query views to process and analyze data.

> Chapter 5 "Changing the Query Selection Criteria"

> Explains how to change or refine the set of information a query retrieves from a database.

> Chapter 6 "Analyzing Data"

> Explains how to use calculated field, totals, and subtotals to analyze data.

> Chapter 7 "Modifying Display Fields"

> Explains how to add and remove display fields and change display field properties.

> Appendix A, "Results Menus"

> Describes the Results menus.

> Appendix B, "Comparison Operators"

> Describes the comparison operators you can use in a `WHERE` clause.

> ### Using this manual

> You need not read the entire manual in detail. A good strategy might be to skim through once quickly, then go back and read for detail only those chapters relevant to your situation and needs.

> ### Typographical conventions

> This manual uses the following typographical conventions:

> Convention | Description
> --- | ---
> Bold | Bold typeface indicates commands or characters the user types, or the names of user interface elements.
> Italic | Italic typeface indicates the title of a document, provides emphasis, or signifies new terms.
> SMALL, BOLD CAPITAL LETTERS | Small, bold capital letters indicate OpenEdge™ key functions and generic keyboard keys; for example, GET and CTRL.
> KEY1-KEY2 | A hyphen between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL-X.
> KEY1 KEY2 | A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
> Syntax:
>     Fixed width
> | A fixed-width font is used in syntax statements. code examples, and for system output and filenames.
> `Fixed-width italics` | Fixed-width italics indicate variables in syntax statements.
> `Fixed-width bold` | Fixed-width bold indicates variables with special emphasis.
>     UPPERCASE
>     fixed width
> | Uppercase words are ProgressŪ 4GL language keywords. Although these always are shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
> | | A vertical bar indicates a choice.
> ... | Ellipses indicate repetition: you can choose one or more of the preceding items.

> ### OpenEdge messages

> OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

> - Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.

> - Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.

> - Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

> After displaying a message, OpenEdge proceeds in one of several ways:

> - Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.

> - Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.

> - Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.

> - Terminates the current session.

> OpenEdge messages end with a message number in parentheses. In this example, the message number is `200`:

>     ** Unknown table name table. (200)

> If you encounter an error that terminates OpenEdge, note the message number before restarting.

> #### Obtaining more information about OpenEdge messages

> On Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

> - Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.

> - Choose Help Messages and then enter the message number to display a description of a specific OpenEdge message.

> - In the Progress Procedure Editor, press the help key (F2 or CTRL-W).

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