list box versus combo box

[worldsci]

I have a field (fd87) where I want the user to choose A,B,C or D or leave it blank .. there are no other options

fd87 has as its RowSource a table (t73), with the values A,B,C,D in it .. there is another field in this little table that contains data which in effect explains what A means, what B means, etc.

now, if fd87 is a list box, when the user looks at a record, the value "A" appears in fd87, unless he/she or another user has chosen B,C, or D on a previous occasion .. but if the user wants to leave the field blank, he/she appears to have no way to do this

a combo box avoids this, but allows unwanted data to be entered

is the answer to this simply to incorporate a blank value, in some way, into t73?

 

[Knicks]

If the combo box is tied to a row source like you said it should not allow unwanted data, only the data tied to the row source.

Its been my understanding that the main difference btwn list box and combo box is that the list box is always open and the combo box is generally closed in appearance.

I prefer using a combo box, you should have no trouble, it will restrict data the same way your list box would

 

[worldsci]

after sending my message, I left the properties sheet open and went to get something to eat .. when I came back, the first thing my eye fell on was LimitToList .. all you have to do is set this to "yes" .. sometimes you have to ask a dumb question in order to find its answer, it seems