Just from reading the source code, I found that the keyboard dialog code in the OS could be tweaked to fix this particular bug. However, there may be other similar bugs, and even if there aren't, your app needs to work on existing devices which have this bug. Sure, you might get around it by disabling the keyboard dialog in your application, but it's still a risky thing to do.
On the one hand, I can definitely understand the pressure you get from your client to do immediate validation. However, I think there really are better ways to solve these problems in most cases. Some examples: Every time any field in the form changes, you run a validation test and update an on-screen indication to indicate whether the form is valid, and if not, why not. For example, it might say "Enter last name" or "Invalid zip code". This means the user can always tell whether the record they're entering is valid. If the user hits the Done button to leave the form while it is invalid, a dialog pops up instead, training the user to look at the on-screen validity indication. If a HotSync is done while there is an invalid record being entered, let the HotSync run, ignoring the invalid record, but when you're notified that HotSync is done, use the alarm manager to present a dialog informing the user in no uncertain terms that they need to correct or complete the entry and HotSync again. This dialog, plus the dialog on their PC about viewing the log will both act as deterrents. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
