>>It seems to me that checkboxes are even worse than other controls, because in the interactive change event, this.value (even from WITHIN the checkbox!) always returns the value of the checkbox _before_ the change, whereas other controls give the value after the change. I have also tried issuing a dodefalut in this event, but it doesn't seem to help. Since a checkbox is either on or off, and there is no in between, and you can be sure that if somebody has changed the value, then the value that returned by this.value is exactly opposite of the real value. Using this to my advantage, I have come into the habit of using the opposite value for my calculations. A pretty kludgy workaround, but it works.
>>While we are on the subject though, another complaint about checkboxes is their noticeable lag in response time. Clicking a checkbox twice within about one second only changes the value once. It seems that it takes this long for the control to internally 'reset' itself before it is ready for more interaction.
>
>I agree. I've had the same problem.
>
>Barbara

It almost seems like you want to use another object to simulate what a check box does.