>Hi Andrew,
>
>Actually, I don't have the ControlSource property set. Based on the 'X' in the box, a routine is run to figure out what date should be populated (it's not the calendar date). In addition, I verify that the number of boxes marked equals the freqency (monthly=12, quarterly=4 etc.). On top of that there are verifications to populate an audit trail and clear out previous dates in a related table. It's hard to explain. Nonetheless, only after all of the verifications are correct do I actually want to update the date(s). I have 'almost' figured out a way using the replace command for each of the 12 dates, but I'm still hoping to get around that. I'm dealing with a table buffering error now - stil plugging away on that one.
>
>Regarding the data control suggestion, in theory it sounds good, except for the fact that I will have the same type of problem on another form which has 36 date fields. The thought of doubling number cringe (especially since the form is quite congested already).

Hmm. Might it not be a better solution to put the varying number of dates required into a cursor and display a grid on the form? Not evryone likes Data entry grids, but it would keep the interface consistent.

Chris.