Bryan,
Why are you using the valid event of the command button cmdAdd? If the commandbutton has the focus while the user is typing, the keystrokes go to the commandbutton, which ignores them. If cmdAdd is used to start some add rountine, use the click event and then SetFocus on the next control to type into.
HTH!
Mark

>I have a VFP 5.0 compiled app running on NetWare 3.12 with a Win95 client. This application used to be a DOS app until it was recently converted to VFP. When the user is doing heads-down data entry (which includes pressing enter on an Add button to add a line item to an order), the code in the cmdAdd.Valid method takes a little longer to process than it did in the DOS version. The user never stops keying after the Add button is pressed. Now that the processing takes around 1-2 seconds longer, whatever keystrokes are entered in that time are lost and then the flow gets *totally* interrupted.
>
>I've checked SET TYPEAHEAD. It's set to the default of 20. There are no obvious commands in the cmdAdd.Valid method that would consume the kestrokes (INKEY(), etc.)
>
>Any suggestions? I can't tell the users to go s-l-o-w-e-r. :)
>
>Thanks.