>The oTemp word shows after the 1st doc' is .Closed. And when Foxpro code stops to pop a dialog asking for info. Which is really bad, Foxpro is waiting for the user to press ok, while the user is looking at a full screen, empty, word session.

The .Save command is forcing Word to show itself, as it's waiting for user input. A way to get around this is to use the .SaveAs method, and specify a filename:

oWord.ActiveDocument.SaveAs("D:\Documents\ThisIsNew.DOC")

>My first append ask whether I am taking the wrong approach.
>Does anyone have a better idea how I can update a user selected set of doc's and end with one doc for the user to edit/print?

The way you've outlined it looks good -- you just have to wrastle with Word wanting to show itself! You're close to conquoring it!

Word has a number of ways to do things like this. You could also look at the Master Document feature, which makes one document behave like a index, providing live links to other documents. However, I think that complicates things, especially if you want an end document that doesn't need to point back to the originals. I'm sure there are still others, but I vote for the simple version, which is easiest to code and maintain, and easiest for the users to use.

Let me know how SaveAs goes, and if it solves the problem.

- della