Cetin

We are using Word97 (no client has yet updated...)

Using code similar to yours we can easily create the word automation object, open a word document, make a few changes, then make it visible and activate it... and it comes on top *the first time*.

We need to leave Word open because clients complain at the extra time taken to instantiate Word; also we can have more than one doc open at once for this app.

If you repeat the above exercise with Word already open, instead of coming to the top, Word just flashes in the taskbar in Win2000.

It isn't just Word, the same happens with Help in VFP; the first time you press F1, Help comes up on top but it you leave it open, after that if you press F1 Help just flashes in the taskbar and you have to select it.

Even using oWordAutomation.wordbasic.appactivate() which definitely used to bring Word to the front and says so in Word help, just causes the flashing. It seems to be a Win2000 "thing".

If you do an append general link followed by a doverb(-2), it *always* brings Word to the front whether already open or not. Which is what we have reverted to. But it seems a lot slower than using normal Word automation.

We tried getting Word's window handle and activating that, but all users did is have more than one copy of Word open and... you guessed it!

We tried using Windows Scripting Host to activate the document, which is *very* quick, but then struggled to get Word Automation working properly on the open document.

Any suggestions gratefully received!

Regards

JR