Perhaps I do not understand it. As in VFP Help for the keyboard comamdn

"The characters remain in the buffer until Visual FoxPro looks for keyboard input.". So when does VFP look for input?


>Hi, Yuri.
>
>>I need to make sure that keyboard command is completed, and only after that run the next line.
>>
>>I do not think it may help, but in real situation I navigate on the form with the keyboard, then take properties of the current control. So what happens is that it first take property of the current control, then implements keyboard.
>>
>>The strange thing is that some other people do not see this behavior, but I see it on FPD2.5, VFP6/7/8.
>
>As Sergey said, what is happening is totally correct.
>
>When you issue: KEYBOARD "hello", five characters are stuffed to the keyboard buffer.
>
>When WAIT WINDOW "hello" executes, as usual, it takes the first character out of the buffer (the only thing it needs to close itself), and execution goes on.
>
>If you issue:
>

>KEYBOARD "hello"
>WAIT WINDOW "h"
>WAIT WINDOW "e"
>WAIT WINDOW "l"
>WAIT WINDOW "l"
>

>you'll get a single "o" in the command window. This is exactly what the commands are supossed to do. I'm sorry that we aren't understanding what you need.
>
>Try to give us more details. I would be surely some solution.