Another possible option is not to allow input via the built-in keyboard and use your own.
> Scott Jocobs wrote: > > > > The field is already restricted to 3 characters and numerics only. > > By handling the keyDownEvent I am able to restrict the user's > > input and > > keep the numbers within the appropriate ranges. However, > > when I use the > > keyboard dialog I never get the keyDownEvents, presumably since the > > dialog's event handler is getting them. Therefore the user can enter > > numeric data outside the valid ranges. > > > > We found that when the keyboard dialog was dismissed a 'fldChangedEvent' was > sent. By handling this event in your form you should be able to stop the > user entering invalid data via the keyboard dialog. > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
