Len The shift-click doesn't seem to work in reverse. In other words, you have to always click at the earliest item and then click the latest item (i.e. crackerbread to apple) but it doesn't work if you do apple to crackerbread because it looks for the items that come after the first clicked item.

I'm thinking if you stored the record ID or time during the click events, you would have the last-clicked record available for the shift-click event.  You could then run a procedure to change all records between the last-clicked record and the shift-clicked record, excluding the last-clicked record.  Additionally, you would have to clear the stored record when you change days and also ignore the shift if shift-click is performed without a last-clicked record stored.

Hi Donald, Thanks, I can see what you mean. So, I'm glad to find out it's not me! Perhaps I should have waited for F52

Matt, yeah, I'm gonna wait for F52

Yes, that is correct. The way that I programmed the shift click is you have to start with the earliest one and end with the latest one. It won't work in reverse. But Matt's idea is also correct. You could store in a variable the first record that you clicked on, and then if the shift click was before that, you could program it to go backwards. I'm not going to do that, but it's certainly possible. L o l.

One other issue, if items, let’s say 2,3,4,6,7 were checked, and you wanted to clear 2-6. You would click on item 2 and shift-click on item 6, wanting all to clear, but they won’t. I know it’s a weird issue and probably not often used but it might be. I was the programmer at work that staff would bring their programs to, to be broken lol

Hi Jerry I just tried a few different things. 8 items checked. Click 1 and shift click 8 they all clear. Repeat with Click 2 and shift click 8 it leaves 2 and 3 checked. Repeat with 3 and 7 it leaves 4 checked. lastly with 9 items it works perfectly! I think I'll check them one at a time in future.