>>>>The light is .click'ing on for me. It looks like we're both right! I don't use a cmdSave button (but rely on a toolbar equivalent I built that calls _screen.activeform.save(), or keyboard navigation that does thisform.save() defined in the form's keypress event). When I added a button with a cmdSave.click holding thisform.save(), everything worked exactly as you described. When I used the toolbar or my hotkeys, it failed as I described.
>>>>
>>>>Looks like the only difference is that by using the command button, my last edited field looses focus before the tableupdate() fires. With the toolbar, it doesn't. I'll play with it for a while. Thanks for bearing with me.
>>>
>>>I think you could try to move focus off control programmatically.
>>
>>That's what I did a few weeks before, work's greate. The keyboard navigation doesn't react
>>exactly the same as the mouse.
>
>Sonny
>
>I just got your note as I was replying to the other. What exactly did you do to solve the problem?
>
>Bob

When you press the button on the toolbar, or use the shortcut, the valid and the lost
focus doesn't fire. Because, you don't change the focus on the current form. So I had
a cmdBox (Sounds like a patch, smells like a patch but it works). So when I fire the
shortcut or toolbar, I set the focus (Explicitly) on the cmdBox) so the valid and
lostfocus launch normally. That's the trick.

P.S.: I don't like to patch things but this one is an exception...