Help! Designing a two-block form.

From: Steve Frampton <2843600_at_jeff-lab_at_queensu.ca>
Date: Wed, 8 Sep 1993 14:11:31 GMT
Message-ID: <CD1Gr8.MFK_at_knot.ccs.queensu.ca>


Hello:

I am new to SQL*Forms and am trying to design a two-block form. I have no training and no access to manuals. What I have learned thus far I have gleaned by reading pre-existing .INP code (which is surprisingly informative).

Before I ask my question, let me show you an example of what I am trying to accomplish.

   Location: _______  [                                                ]
   
   ---------------------------------------------------------------------
   
   Employee ID: _____  [                            ]  Job: [          ]
   Absent From: ______  To: ______  Reason: ____ [                     ]
   
   Employee ID: _____  [                            ]  Job: [          ]
   Absent From: ______  To: ______  Reason: ____ [                     ]
   
   Employee ID: _____  [                            ]  Job: [          ]
   Absent From: ______  To: ______  Reason: ____ [                     ]
   

The way the form is supposed to work is, the user queries a location code and brings up a work location. Then they are brought to the next block, where all the employees who work at said location are displayed (from the "POSITIONS" table). These employees' absence information can then be entered (which ends up in the "ABSENCES" table).

The way it works now, with my limited knowledge, is that the user can query a location successfully...but must then move manually to the 2nd block. No employees are brought up automatically, but I use a POST-CHANGE trigger to bring in the name and job fromm the "POSITIONS" table after an employee number is typed in. There are some other minor problems too, however I think I'm already on track to solve them.

This has been tricky to explain...to sum up, a location is query from the 'LOCATIONS' table. All employees are brought up from the 'POSITIONS' table 'WHERE POS.LOCATION_CODE = LOC.LOCATION_CODE'. The fields {ABSENT_FROM, ABSENT_TO, and ABSENT_CODE} can then be updated into the 'ABSENCES' table. In short, I would like to know how these employees can automatically be loaded and displayed, whether there are 3 or 300...allowing the user to navigate between them using the <UP> and <DOWN> keys.

Any information would be *greatly* appreciated. Please respond via e-mail to '2843600_at_jeff-lab.queensu.ca'.

Thanks in advance.

--< Don't forget to vote for soc.couples.intercultural on Sept. 14/93 >--

Steve Frampton                     Home:   <frampton_at_vicuna.ocunix.on.ca>
Kingston, Ontario                  School: <2843600_at_jeff-lab.queensu.ca>
Received on Wed Sep 08 1993 - 16:11:31 CEST

Original text of this message