>> Then do not call Quit() (VFP already has control - check those messages printed in VFP window. Maybe you mean window.activate).
>The messages NEVER appear in a VFP window because the automation process that instantiates Word does not have a user interface. Messages don't appear at all except when I run the code as a stand-alone prg from the command window. Then they appear on the desktop. The balloon in your code sample never appears under any circumstances. Perhaps that is a problem with Word 12?
>
>VFP app does this: open word, create document, call WordEvents.prg (for editing)
>Wordevents.prg does this instantiate eventhandler, make word visible for editing, and SHOULD return control to VFP app upon Save? Print? Close? I really don't care what event at this point.
>
>Here's what I observe: 1) WordEvents executes and there is no pause for editing (the VFP app continues on the following line), or 2) Word opens for editing and the VFP app does not continue until after oWord.Quit()

I surrender.
Cetin