Selecting and entering multiple values in this fashion seems a poor interface design. Short of some very complicated scripting driven by the OnObjectkeystroke trigger, I see no way to do what you want. But there are many alternative methods for selecting multiple values and I would generally use a related table to list the multiple selections so that I can put each value selected in its own related record.
Yea, from a data collection perspective, it probably seems quite haphazard. It is basically a list of conditions a patient might have that we must be aware of, but not necessarily do anything else with, other than to collect the data and display it. It is simply there to ensure that we know about it/them. Unfortunately in this day and age, people rarely have one condition...they usually have high blood pressure combined with diabetes, along with 3 other health issues. The users of this database won't treat or track those conditions, they just need to document that they know about them.
I had thought of using a repeating field, but it's very hard to know how many of repetitions to have.
I see your point to using a related table, I'm just not sure the data is that important to track that specifically, other than for interests sake in research.
Thanks, I'll think about which way to go...perhaps I should just put the little extra work in....
And this sounds like something for which I would set up a related table with one such condition recorded in each related record. A portal would make it very easy to record this information and you can record as many or as few as needed when you do so.
And I strongly recommend against using a repeating field here.
Yea, you're right. I'll put in the little extra work it takes and do it the right way :)