I am writing a VB6 program to search and replace text in a Word document.
I have tested the program and it works fine with the version of
MS Word that I have loaded onto my machine. In my VB6 Project properties
I made reference to the MS Word Object Library that is installed
on my computer.
I want to package and deploy this program, however I'm sure I'll be faced
with the reality that not all users will be running the version of Word
that I have.
I used the VB6 Package and Deploy Wizard to create the setup.exe , .lst and
.cab files required to install it on another computer which doesn't have the
same version of Word on it.
After the installation on computer #2 I reviewed the ST6UNST.LOG file and noticed
that the Word Object Library file from computer #1 had been copied onto computer #2,
into the WinSysPath, however it was not registered.
Question #1:
Should have the Object Library file been registered, and if so what would be the
proper variable to use in the Setup.Lst file (i.e., $(DLLSelfRegister), ) ?
Question #2:
Do I need to have the Object Library file in my CAB and will I need to have the
Object Library files for each version of Word referenced and compressed into my .cab file?
Question #3:
If not, can I simply make a reference to whichever object library the user already
has on their system.
Question #4:
Can I prompt the user during runtime, and ask them for the path/filename of the
object library their version of Word uses and would this be a good alternative?
Maybe I haven't asked the right questions or put them in the correct order, but I hope I've given enough
background to let you see where I want to go with this?
Thanks much for any insight.
Code examples would be appreciated.
