When you write out a statement describing the data you want to collect, it is import to specify if any of the fields mentioned need to hold multiple values, as that has a big impact on the design.
<hr>I want to record the level of pain experienced by each patient at each visit and whether it is constant or intermittent and the type of pain<hr>
I thought that by breaking the description of pain into different dimensions you would only need one value for any one dimension.
But I don't know enough about pain categorisation to know if that is true.
One dimension is the Intensity of the pain. Another dimension is whether it is constant or intermittent. A third Dimension seems to be some more descriptive term such as "Stabbing" or "Sharp", and I think it is here that you think you need multiple values.
The general principle is that whenever you need multiple values you move the data into a related table, and display it on a subform ( or if you prefer and use 2007, create a multi value field, and perhaps display it as a list box .)
So the visits table would have:
<UL><LI>a field for Pain Intensity (displayed as a combo box, with its own list of values)
<LI>a field to describe the continuity of the pain (displayed as a combo box with its own list of values[/list]Then I would create a new table tblVisitPainDescription - VisitPainDescrptionID autonumber, VisitID Number and PainDescrption. PainDescription would be displayed as a combo with its ow list of values.
These PainDescription would be displayed as a subform on the Visits form.
If you prefer the multivalue field option, add PainDescription to the Visits table as a multivalue field, with its own list of values.
I don't know about the other problem. It sounds like the form has become corrupted. What do you see in Design View? Can you remove the list box? Have you tried "compact and repair"?