Visual Basic, Using equivlent Msword8.olb in Office 2000

Using equivlent Msword8.olb in Office 2000

Author	Message
BBM Software Servic #1 / 3	Using equivlent Msword8.olb in Office 2000 I have an application that uses Word8 that shipped with Office 97. I don't have office 2000 and really don't want to buy it if I can help it. But do want the application to work with Office 2000. Right now my program reference is Msword8.olb and uses word.application and I am thinking that if I have two installs one for 97 that references Msword8.olb and one for 2000 that references MswordX.olb(and at this point I don't know what that is, if someone could tell me that would be nice). Can anyone see why I can't just edit the reference and do a build and have it work???
Mon, 10 Nov 2003 21:48:32 GMT

James Can #2 / 3	Using equivlent Msword8.olb in Office 2000 The best way to ensure cross-version compatability is to late bind. Instead of having a reference to Word, remove the reference and use CreateObject("Word.Application"). Change your variables from Word.Application, Word.Document etc. to Object. It's slower, but it will ensure better compatibility Quote: > I have an application that uses Word8 that shipped with Office > 97. I don't have office 2000 and really don't want to buy it if > I can help it. But do want the application to work with Office > 2000. Right now my program reference is Msword8.olb and > uses word.application and I am thinking that if I have two > installs one for 97 that references Msword8.olb and one > for 2000 that references MswordX.olb(and at this point I > don't know what that is, if someone could tell me that would > be nice). Can anyone see why I can't just edit the reference > and do a build and have it work???
Mon, 10 Nov 2003 22:58:07 GMT

BBM Software Servic #3 / 3	Using equivlent Msword8.olb in Office 2000 Thank you. Your right on both accounts, it works slick but slow. But I will take it all day long, the alternative was making me a little ill. Thanks again. Quote: >The best way to ensure cross-version compatability is to late bind. >Instead of having a reference to Word, remove the reference and use = >CreateObject("Word.Application"). Change your variables from = >Word.Application, Word.Document etc. to Object. >It's slower, but it will ensure better compatibility >> I have an application that uses Word8 that shipped with Office >> 97. I don't have office 2000 and really don't want to buy it if >> I can help it. But do want the application to work with Office >> 2000. Right now my program reference is Msword8.olb and >> uses word.application and I am thinking that if I have two >> installs one for 97 that references Msword8.olb and one >> for 2000 that references MswordX.olb(and at this point I=20 >> don't know what that is, if someone could tell me that would >> be nice). Can anyone see why I can't just edit the reference >> and do a build and have it work??? >>=20 >>=20
Tue, 11 Nov 2003 03:14:16 GMT

Page 1 of 1

[ 3 post ]