David,
In retrospect, that makes perfect sense. Earlier today I was able to completely fix this problem simply by calling SetFocus, followed by LostFocus, on the current control from within my Save method.

Thanks for all your input!

Ed

>Ed,
>
>Buttons in toolbars do not get focus, so they don't cause a form control to lose focus. That's why the code like _screen.ActiveForm.ActiveControl.SetFocus() is required to get the current edit committed to the ControlSource.
>
>>When the toolbar button is pushed (or a menu control, for that matter), should the active control lose focus anyway? Or is it proper that the "clicked" method occur first, then any other methods for the previously-active control?