Re: Display only blocks in SQL*Forms

From: <champs_at_hhcs.gov.au>
Date: 14 Jan 93 09:47:46 +1100
Message-ID: <1993Jan14.094746.577_at_hhcs.gov.au>

In article <1993Jan13.190453.17942_at_eng.ufl.edu>, mjw_at_mailbox.eng.ufl.edu (Mike Wohlgemuth) writes:
> I need to create a form in which the user enters information
> to be used in a query, and the query results show up in a
> seperate block in the form. The form should allow them to
> enter the block and navigate through the results, but not
> allow them to edit the values in the results. I have RTFMed
> and cannot see any way to make all the fields in a block
> display only and still be able to enter the block. Am I
> missing something obvious?
>
> Mike

Your best bet is to add an enterable non-database field to the display block. This way you can show the block and not worry about what they might type in the field as it's never going to be commited to the database.

If there are several pages of results, put a field on each page and use a KEY-NXTFLD to navigate to the next page (and even a KEY-PRVFLD to navigate backewards).

If you have multiple records in a list of results, you should create an enterable non-database 'cursor' field in the same multi-record block that you use to display the results. Then let the user scroll up and down the list til cows come home.

Hope this helps.

---

    /\       Steven Champness (champs_at_hhcs.gov.au)
   /  \      Dept Health Housing and Community Services
  /    \     Brisbane Queensland
 /      \     via

/ / \ Canberra Australia
\ / / /
 \/ / / / MACINTOSH SOFTWARE AXIOM : If you need a manual to operate it

  \/ / /                                it wasn't designed properly in the
   \/ /                                 first place !

    \/ Received on Wed Jan 13 1993 - 23:47:46 CET