Okay, well, the initial point was that even MS doesn't make everything easy to get to with the keyboard. VFP 3.0 is a good example. And I was only responding to your "correction" of my statement that Windows is geared towards navigation through use of the mouse. I don't know why you felt you had to argue that point. I think it is obvious. Workarounds are required for keyboard navigation a lot more than mouse navigation. You can simply look at the VFP Project Manager in 5.0 where they actually made the keyboard work (through form-specific hard-coding I am sure...which is why it didn't work in VFP 3.0) and tell me what is easier to use, the mouse or the keyboard.

Just because the Windows standards tell us that things have to be accessible through the mouse AND keyboard, doesn't mean the keyboard will access these things as easily.

Joe

>
>I checked this out. If works properly in VFP 5.0, but not in 3.0.