Thanks Joe,

You're right, I'm pretty sure of what I want. I guess the _real_ question I wanted to pose is whether there is any defacto standard for systems like this?

And, if there are, I'd sure like to see some examples...

You know how a lot of systems use the standard where the navigation buttons are along the bottom edge of the form and each form has it's own set of nav buttons? Then there's another 'standard' where the nav buttons are on a toolbar at the top of the screen and the same nav buttons apply to whichever form is active. Well these are perfect examples of 'mouse-centric' systems... there's no (obvious) way to navigate records without using these buttons.

The reason I'd like to see some examples of a 'keyboard-centric' system is so I can learn the 'right' way to do it (if there is a 'right' way... which is also my question)

Thanks for your prompt feedback...

>We have some forms where this idea is used (keyboard only, data entry, pageframes for tonnes of fields)...I can't show you our system though...just deal with every problem (where a mouse in 'needed') you run into on an individual basis and you will be done...I don't think you need any example...you know what you want, you just have to envision it and program it...
>
>Just my opinion...
>
>Joe
>
>>Is there an example anywhere of a practical VFP system that is heavily transaction oriented and designed for heads-down data entry?
>>
>>All of the Windows programs I've seen rely heavily on the mouse and therefore, slow down a dedicated data entry person's production because they're having to reach away from the keyboard and back... I know what you're thinking, but those seconds add up over time :)
>>
>>Any thoughts... ideas??
>>
>>Thanks