>>Nodefault and stuffing the keyboard buffer works fine. Strange way to "eat my sandwich" but it does the job. Looks like MS would have provided a way to pass a different value back to the object directly from within the keypress event. Many thanks for the help.
>
>Mike,
>
>If you must do it that way then here's an experiment to try, in the Keypress;
>
> IF nKeyCode =
> NODEFAULT
> nKeyCode = ASC("")
>ENDIF

Jim,

I tried that first but there seems to be no way to return the new value to be processed by the text object. nKeyCode is a local variable the key value is passed to. Using the Keyboard approach works fine. I just had some concern with "fast" typers on a slow machine getting an extra keystroke in causing a sequence error. No, I don't want to clear the buffer.

Regards,
Mike