Multivalue Field Advice

[June7]

The multi-value field would not be 'linked' to anything. It would go away.



You have to create a table and then input individual record for each item that was an element of the multi-value field. And yes the child table needs the parent ID as foreign key.

Might be able to use a query that expands the elements to individual records and then make table from that query. Review http://office.microsoft.com/en-us/ac...010149297.aspx

[Leonidsg]

Okay I understand the Child table setup to avoid the multivalue field, at least I think I do. I have been working on the combo lookup table setup and there are two ways I can go about it.
1. In the table set the field as a lookup field and when creating the form, drag that field into the form and a combo box will be created
or
2. In the table make the field a text box and then in the form make a combo box with the RowSource set to the lookup table and a the control source set as the text field.

Please let me know which setup you think is best.

Thank you

[June7]

My personal preference is to not set lookups in table if there is an alias involved. As developer, when I view tables I want to see the real value in the field, not the related descriptor.

[Leonidsg]

Perfect Thank you for the help once again.