>>>>Tip: Whenever I'm having trouble with Office Automation, I go into the Office app and record a macro to do what it is I need to do, then look at the VB Script in the macro.
>>>
>>>Ken, just when I think I've got everything under control, I try this and the syntax heads off into never-never land where VFP doesn't follow. Usually a couple of inspired guesses (oxymoron?) will get me back on track, but I sure wish VFP would supply a cheat-sheet for all of the Office commands.
>
>I hear your pain < g >. Those global constants that are built into the OLB files should be available to VFP. Here's how to see them:
>
>Go into tools\macro\visual basic editor. Go to Tools/References. You will see a listbox of all registered OLE controls and servers. Put a checkmark next to Microsoft Office 8.0 Object Library. Click OK. Now press f2, which will bring up the VB Object Browser. You will see a combobox that says < All Libraries >.
>
>Open that combo box and choose Word.
>
>In the left pane, you will see an entry at the top called globals. Click on it and you will see all the globals. Click on the constant in the right pane, and at the bottom of the screen it shows you what value.
>
>Menachem Bazian exported from either this browser (or its equivalent in VB) to a file and then parsed the file into a .H file for VFP.

Thanks - and remember that HTML won't allow angle brackets unless there's a space inside them.

Barbara