>>I am having a problem in the direction I want to head. I was hoping to use a DROPDOWN List for eye color. However, I am seeing data in the main data table where a person has one eye that is GREEN and a 2nd eye that Is BLUE, or vice versa, or lots of other variations.
>>
>>How on earth do you handle these multiple eye colors? Do you have to stick with a TEXTBOX only where the usr types in anything, or is it conceivable that you could possibly imagine and enter into a PICKLIST table all the variations on eye colors?
>
>Last time I had descriptive colors (i.e. not integers, but text such as is used in the app's domain), I used a simple textbox with autocomplete set. And whatever they (me, that is, since I used that app) put in there, would be offered. Turned out to be quite a limited list, even with color1/color2 (e.g. beige/brown, yellow/orange), and a very simple solution. Sure, there was no lookup and no integrity enforced, but then with what people call colors, you may not want to try to enforce any rules. It's all too subjective.
>
>Specially for eye color - I've read somewhere that there are no green eyes among humans. What we call green is sort of grayish-olive-ish. Any plant with such a color would wilt, suffocated by lack of photosynthesis. Still, your users will want to enter green - so let them. If your business rules allow that, though.

You can really be a nitpicker sometimes <g>. Eyes are not green, they're "sort of grayish-olive-ish"? Don't you think "green" gets the idea across succinctly? I doubt anyone is going to be left in the dark by that.

Lucky me, I had a green eyed girlfriend. A green eyed redhead. Double lucky me.