Hi Dale

I agree with you, however, I took a different approach to solving it.

I use a form class that serves multiple purposes. It is a data entry form, with a grid and an area for the user to enter search criteria on the first page. This same class can be used as a picklist form.

Instead of a combobox, I use a modified textbox. The user's entry is validated against a table/cursor. That same table/cursor is the source of records for the grid on the corresponding picklist form. The user can add one or more records to the picklist form. They can also edit, find and delete entries.

This may seem like overkill for the simplest lists, but if I use this approach in all cases, it becomes very familiar to the user and they don't make as many mistakes as they will when presented with several different ways to maintain related lists of information.



>This is something I would recommend against doing.
>
>I did this a couple years ago for a customer and you wouldn't believe the "junk" that was added to the table..........poor spelling, all lower case, all uppercase, duplicate entries due to typos, etc.
>
>What I ended up doing is supervisor password protecting a maintenance form for doing things like this. It was inconvenient at first, until they got most of the entries they really needed.
>
>>I have a combobox on a form where:
>>
>>ControlSource is Table_A.Material
>>RowSourceType is 6-Fields
>>RowSource is Table_B.Code
>>
>>I want the user to be able to add in a new item (not in already in Table_B)and to have that item added to Table B.
>>How can I do that?
>>
>>Thanks in advance
>>Raymond Larche