>I think you could greatly simplify your code by doing your hot key magic >inside the interactivechange event or keypress event. Doing this you could >eliminate the timer completely and make the code easier to follow.
>
>Bob

Ya, I'd prefer to do that myself, the funky thing is I've got a requirement to respond to key combinations like ALT+CTRL+Z. For starters keypress doesn't pick them up, neither does interactive change. Indeed keypress won't respond to anything with ALT in it, and about half the alphabet is already reserved for various CTRL+whatever function keys on the form so they want an pretty wide range of key combinations for the macros.

On Key Label is also not so hot because it won't take the ALT+CTRL functions either. Thus there is this stupid timer that is constantly scaning the keyboard buffer for these kinds of keystrokes in combination. Its ckunky like an old Buick, but its getting the job done,(sort of). I wish the original programmer had not been so "creative" with this solution, its in 3 generations of our product and our user manuals so there is no going back on it now. It's pretty wacky code. It uses a bunch of macroed on key label commands that do pretty much nothing so that the key strokes that would normaly go into the control events just sit in the buffer instead so this thing can scoop them out. I would love to give it the deep 6 if I could.