Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 19 MAY 2008 01:36:24PM Mat Kelly wrote:

I'm working with an existing application that was originally built in Arev31 and has been ported to Arev32/OI.

On a window there is a field "Week Number" that acts as a key (just in terms of correspondence, not as a lookup) to other respective fields, i.e. a MV.

In Arev31 (where there is no "mandatory" attribute to a prompt), when this Week Number field's value is deleted via Ctrl-X, the user can deselect the field, edit other things in the window and go back to the field to enter a desired value.

For some reason, in the conversion to Arev32, this field picked up the mandatory value of "yes". The behavior of this field in Arev32 is, when the value is Ctrl-X'd and moved out of focus, an error occurs stating:

M114

The master prompt for an existing AMV row has to contain a value.

-

Enter a value at this prompt or hit Crtl-D to delete the entire row.

Thinking I would be clever, I toggle the Mandatory field to No and saved the prompt. I do so, exit paint, re-open paint and the "Yes" value is restored. Running the window, regardless of my change, exhibits the same behavior.

How do I go about replicating the behavior of my Arev31 application? Am I missing something fundamental?

Thanks.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/929fa67fd77c1aa38525744e0060b796.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1