- Local time
- Yesterday, 21:31
- Joined
- Feb 28, 2001
- Messages
- 30,194
I'm going to speculate here. It is possible to cancel a double-click because there is a Cancel parameter in the call sequence. We can't see a cancel option for the single-click - but Access can. I looked it up and there is no comment on it, but I'll bet that when Access goes to implement the click that would normally update the button, it finds that it can't so does a Cancel that we can't get to - because it has to cancel the update. Understand, this is all speculation.
@Tera, can you just unbind the checkbox and get THAT to click? You couldn't update your original underlying query because it was not updatable, so it seems that it shouldn't matter whether the checkbox was or wasn't checked originally - you aren't going to change it. I would think that you ought to be able field a click on an unbound control. I know I have used a double-click on a label as a "backdoor" trigger to start a sequence that, if I did the right things in the right order, would unlock a locked DB. According to the MS documentation site, a single-click is legal on a label, and that would be just as unchangeable as bound control that can't be updated due to the underlying recordsource.
@Tera, can you just unbind the checkbox and get THAT to click? You couldn't update your original underlying query because it was not updatable, so it seems that it shouldn't matter whether the checkbox was or wasn't checked originally - you aren't going to change it. I would think that you ought to be able field a click on an unbound control. I know I have used a double-click on a label as a "backdoor" trigger to start a sequence that, if I did the right things in the right order, would unlock a locked DB. According to the MS documentation site, a single-click is legal on a label, and that would be just as unchangeable as bound control that can't be updated due to the underlying recordsource.