If I understand this properly, to "show values only from second field" in a drop down list, one 'tricks' the view by putting a text box on top of the one containing the first field. Whereas a pop-up list actually does show the value from only from second field as expected.

Is this correct?

If so, how does one deny user editing of the second field from that layout?

How does one do auto-completion of the foreign ID field that has a secondary display field (the one that ultimately gets put on top of it) while encouraging the user paradigm of using tab to move to the next field?

In my example I have two tables, products and labels. The label_id key from the labels table is in the products table in a one to many relationship. If I use a value list to populate the drop down list, when using an ID field, auto complete is not available (greyed out), thereby killing the tab to next field functionality. I should clarify that while I can actually tab to the next field, it doesn't enter the selected value prior to exiting that field as it does when auto-complete or the enter key is used.

What am I doing wrong?

edit: I should say that the basic goal is to shield users from ID fields, while embedding them in respective tables.

If a user could simply select the label in this case from a products layout to be applied to a given product, without seeing or dealing with the respective ID I'd be happy!

Edited September 3, 200817 yr by Guest

Well, I found the field behavior dialog, which answers a few of my questions about limiting access to a field.

I still don't understand why the drop-down doesn't work like the pop-up showing value lists.