> you cannot pick and chhose which methods you are going to define

I did cut and paste in all of the the additional procedures, but what I missed was that one "slight" change at the top :-)

The whole question about which .olb file should be used took place earlier in this thread. Your comment that "this is a design time issue " was misinterpreted by me to mean that, once compiled, the process would work regardless of which .olb file the class had been based upon. I "assumed" that as long as the event in question was present in the class, the procedure would be interpreted correctly. However, you also said, "you need to create separate handler classes for each version". I guess I glossed over that because it seemed to be an impossible requirement. I have no way of knowing which versions of Word might actually be installed on client machines. Users often work remotely and their home computers were not set up by the IT staff. Workstations should run Word 2000 or greater but I don't even know how many versions that encompasses--or where to get the type libraries for versions I don't own. Any suggestions?





.