>>When I was goofing around I used = CAPSLOCK(.F.) to make sure that it was when it was set to on. It seems (and I admittedly haven't tested this as well as I should), that VFP lags behind itself. While I haven't looked into it closely enough to know for sure, it seemed that VFP executed the statement, then the code that followed. When I looked at the keyboard afterward, caps lock was still on, and the debugger said that CAPSLOCK() was .F. Strange, but I think I may be guilty of some bad (computer) science here. Turn capslock on, insert = CAPSLOCK(.F.) and see what you come up with in my code sample.
>
>That's exactly what I did and it worked. Weird...
>
Hi Vlad,

It could have something to do with the clock speed (350 Mhz) or the keyboard driver. I think you had a better solution.