Browse Prior Art Database

Avoiding Assigning Artificial Names to Tables Used in Panels

IP.com Disclosure Number: IPCOM000036158D
Original Publication Date: 1989-Sep-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 2 page(s) / 53K

Publishing Venue

IBM

Related People

Payne, ME: AUTHOR

Abstract

Disclosed is a new end user interface design which allows OS/2* Query Manager Panels to be designed without the need for assigning artificial table names. The present design uses an artificial name (ROOT, SUB, LOOKUP1, etc.) according to the use of the table within the Panel. By avoiding the need to assign this artificial name, the proposed interface is easier to use and provides better prompting for the end user.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 91% of the total text.

Page 1 of 2

Avoiding Assigning Artificial Names to Tables Used in Panels

Disclosed is a new end user interface design which allows OS/2* Query Manager Panels to be designed without the need for assigning artificial table names. The present design uses an artificial name (ROOT, SUB, LOOKUP1, etc.) according to the use of the table within the Panel. By avoiding the need to assign this artificial name, the proposed interface is easier to use and provides better prompting for the end user.

The new interface allows Query Manager to control the processing without artificial names by presenting separate menus to the user for each table defined for the Panel and for each set of columns to be used to connect any two particular tables. Since Query Manager knows the table names based on the menu presented, it is no longer necessary for the end user to key the artificial table names on the menus. The figure shows an example of a "Table Fields" menu for a Sub table.

The end user will no longer have to memorize artificial names, and there is less keying to do on the menus. Since different information is valid for tables according to their use (ROOT, SUB, etc.), the menus can be tailored for the information which is needed.

Query Manager can prompt the user through a series of menus used to define which tables are connected to each other and then prompt for the columns to be used for the connections. The end user no longer needs to be either totally self-guided or to rely on error messages...