Re: ENTER_QUERY (other than page 1) v3.0

From: Mike Oswald <moswald_at_cwis.unomaha.edu>
Date: Thu, 5 Aug 1993 15:48:33 GMT
Message-ID: <1993Aug5.154833.17271_at_news.unomaha.edu>


p0070621_at_oxford-brookes.ac.uk writes:
>
> Why d'you want to start on page 2? Surely that makes it your first page, ie.
> page 1?
>
> If you want the cursor to change to a different field when the user presses
> enter_query, then write a trigger to do it.
>

The original database design called for using two or more tables for our Hardware & Maintenance data but due to budgetary cut backs the many->one design is more or less one->one.

Anyway ... the primary focus for most of the staff is the hardware info which occupies all of page 1 and the maintenance information is on page 2.

A problem came up when someone wanted to enter a query from a maintenance field on page 2. The only alternative was to issue the enter_query then press the previous_field key at least once may be more (this depends on how you have sequenced your queryable & updatable fields.

Soooo ... I have written a solution in a simple PL/SQL procedure and will post the code here when I get time to work out one little bug (which poses no real problem but it can/might cause some confusion for the customer).

BTW ... page 2 is a pop-up window and with some other minor changes the customer can remain in this window while pressing next & previous_record keys. This is important in my application in that they can still see some vital hardware info while being able to concentrate on the maintenance data.

Mike Oswald
Univ. Of NE Medical Center
Computing Services/Telecomm Received on Thu Aug 05 1993 - 17:48:33 CEST

Original text of this message