I have an application using GUI.fp7 and Data.fp7 and have encountered a usage case I don't understand.

In Data.fp7 I orginally implemented a Value List called Letters containing "A", "B" and "C" as the allowable choices for a text field. And for a reason that I cannot recall, I ended up with an identical Letters value list defined in GUI.fp7

Regardless, everything worked fine until I wanted to add a "D" value. I did so in the GUI.fp7 but got a message saying "not an allowable choice" when clicking on it in a popup.

So I went to the Data.fp7 and added "D". Again, everything was fine -- until I decided that I didn't need "D" after all.

I removed it from the GUI.fp7 and it vanished from the popup choices -- even though it was still defined in Data.fp7

So this has me thinking: what IS the proper way to implement Value Lists in the separation model? Always in Data? Only in GUI? And what are the rules if a particular value list happens to be in both?

Any suggestions or insights will be appreciated.

I think that you may have one value list assigned to the layout field but are using the other value list to validate the field.

I tend to keep all of my value lists in the GUI file so that I can just swap in the GUI file without having to touch the data.

Steve

You are correct. I have Validation by Member of value list = Letters turned on.

I can remove it in Data.fp7 and depend on filtering the user-entered fields. But by removing it I'll lose the capability to auto-validate imports. I wonder if there's anything else to consider other that the easier GUI upgrades that you mentioned?

The bottom line, I suppose, is to just remember that

GUI::ValueList::Letters and

Data::ValueList::Letters

are distinctively different, even though they happen to have the same "first name".

Thanks for the response.