Browse Prior Art Database

Connecting Column Relationship in Query Manager Panels

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

Publishing Venue

IBM

Related People

Payne, ME: AUTHOR

Abstract

Disclosed is a new end user interface design for defining the connecting column relationship between the Root table and the Sub table in an OS/2* Query Manager Panel. Presently, the end user specifies a two character code on the line where the connecting column for the tables is defined. The proposed interface has the end user select the relationship from a list presented on a new screen which is automatically presented following the definition of the tables used on the Panel.

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 98% of the total text.

Page 1 of 2

Connecting Column Relationship in Query Manager Panels

Disclosed is a new end user interface design for defining the connecting column relationship between the Root table and the Sub table in an OS/2* Query Manager Panel. Presently, the end user specifies a two character code on the line where the connecting column for the tables is defined. The proposed interface has the end user select the relationship from a list presented on a new screen which is automatically presented following the definition of the tables used on the Panel.

The figure shows the proposed menu. The user can select the desired relationship and specify how deleting a row in the Root table should effect the connected rows in the Sub table.

The end user can select the desired relationship without having to know a code. The availability of the "Delete rule" field allows the user the ability to explicitly define how deleting a Root row effects the connected rows from the Sub table.

With the present design only one column is allowed to connect tables since having multiple relationships defined would be ambiguous. By removing the field, the ambiguity is removed so multiple connecting columns can be allowed. The 'connecting column' menu is further simplified in that the relationship field had appeared on every line although it was only allowed to be coded on the one line defining the connection between the Root table and Sub table. * Trademark of IBM Corp.

1

Page 2 of 2

2

[This page contains 2 pictur...