Hi Paul,

Yup, but he could get around that to tying F10 (or, preferably to maintain some sort of Win standard Ctrl+S) to a menu option and have the menu option fire code to check ActiveForm.

But this does solve one problem in that a lot of folks (as you know) would tie menu code to screen UI elements that in turn ran custom methods. So you'd fire a Click of a Form button that would run Save. Now you can use RaiseEvent to fire events/methods that don't necessarily have a UI bound caller. Cool, huh?

>Provided your form actually has a save event, yes (I just tested it).
>But that code only works if there is an activeform, if there isn't you'll get an error.