field update puzzler

I'm stumped on this one and would welcome any ideas:

I have a form with the UPDATE_ALLOWED property turned on for the block and UPDATEABLE property turned off for a field in this block. From this field you can do a KEY-LISTVAL to look at possible values (even though you can not update it). KEY-LISTVAL calls another form from which you do the query.

The problem:

        On returning from the form call, the field can now be updated! This, even though I've put message statements in the code to print out the current setting of the UPDATEABLE property. The setting of this property are 'FALSE' all the way up to the last code executed after returning from the other form. Setting the UPDATE_ALLOWED property for the block to FALSE gives the desired behavior but is not a solution because some fields in the block SHOULD be updateable.

I've found a work-around: I set the block UPDATE_ALLOWED property to FALSE on entering the field and TRUE on leaving but I don't understand what is going on after the call to the other form to make my field updateable, even though the property setting says it isn't. Setting the INSERT property to FALSE does not change this behavior (I had thought that for some reason it was believing this record to be 'new').

Any ideas out there?

George Received on Thu Jul 31 1997 - 00:00:00 CEST