> >My users would disagree. They're quite used to have all their errors > >reported on the spot, before they move off the field. In most cases it's > >not an error message, but a lookup table, messagebox or a popup to > >choose a value from, etc. Moving this to the Save button would mean that > >they have to get several fields back to correct the error. > > > Sure. I just want to mention that there is evident difference between > DOS-like (where users tab from field to field) and Windows interface where > users click by mouse. You and me know that most of users complain moving to > Windows, but what can we do with this. Should we accomodate Windows app to > DOS-like features? I don't think so. It's better to repeat the phrase "This > is Windows Standard" until users will get quiet. We still live in (on?) FPD26. I can already hear them "what? Windows standard? We were far better off typing single handed... now we have to use both hands on the keyboard and reach for the mouse every minute... can you get us back to the old program?". All my textbox (except EditBox) etc classes intercept the Enter in the keypress event and emulate a Tab key. Just in case. It's not any slower and it works.