I guess I didn't ask that question clearly enough--or failed to grasp the answer in its entirety! In the beginning of this thread I was concerned about where to get the type libraries for the specific versions. I saw that as a major obstacle from the outset. It's just about impossible to know when the interface has changed unless you can inspect the library--unless you are willing to wait for the code to break :-) Ironically, that is how I inherited this client in the first place. Microsoft discontinued support for Word Basic commands at some point (Word 2003 maybe?) and the application broke when they upgraded Word on a few workstations. Because the resulting wrapper class needs to have code merged and then be compiled, it's not really practical to create it on-the-fly even though the OLB file would be available at that point. And then there are the decimal versions of the Word product. Hopefully these don't have different interfaces! The Word version is already known (largely because there is so much condiitonal code for Word 2007), but at the point handing the document off for editing, it is a bit late to find out that the eventhandler doesn't exist.

I may have to rethink the entire process. I could envision preparing the document, saving it to the user's personal directory and just tell them "Go edit it and print it yourself," but the PDF printer only exists within the VFP application. They may (or may not) have another PDF printer at their disposal.

It is beneficial to have this discussion now though--before I get myself into even more trouble! I have another client whose VFP 7 app prints 60+ documents, all of them VFP reports even though more than half are actually form letters. The users are now asking for the ability to edit those letters after the data has been merged. I was planning to offer them this technique when we meet in February. I guess that will depend upon whether I'm able to solve the version problem and how bulletproof the editing module becomes. At the moment, there seems to be some flakiness surrounding saving and opening the document and a few holes in the editing module where users can do unpredictable things.