Re: Forms4.5 question: Displaying data

Janice Powell wrote:
>
> We have a standard that when doing a SHOW/DISPLAY of data (as opposed to an
> UPDATE) we protect ALL fields. But we're finding that is not so easy to do
> in FORMS4.5 since you have to have atleast 1 updateable field in a block
> before you can say go_block ... to execute_query. I've looked in the manuals
> and have been unable to find a way to say execute_query(blockA) rather than
> having to say go_block('blockA'); execute_query;
>
> I have thought of making an updateable field that has no data in it and that
> is the same color as my canvas -- thus, kinda like an invisible field. Then
> I could go to that and execute_query. But I wondered if there was a better
> method.
>
> Has anyone else experience this problem? If so, how were you able to work
> around it?
>
> Please send replies to powell_at_clemson.edu. Any info will be greatly
> appreciated.
>
> Thanks so much.
> --JP
> --------
>
> Janice Powell
> Clemson Univ.

We have a similar situation in our project. We have a main block where the records have to be displayed but are not updateable and a command button block which contains the different buttons like 'Expand to a certain form' or 'OK'. When creating the main block in the designer, we set the 'UPDATE ALLOWED' to false and 'INSERT ALLOWED' to true. In the querying process, after we do an execute query we set the 'INSERT ALLOWED' to false and navigate to the command button block. This works just fine. Received on Fri Feb 28 1997 - 00:00:00 CET