T
Tony
Hi All,
I've got a database into which I have to import data from MS Word. I
initially made a reference to 'Microsoft Word 11.0 Object Library' for this
purpose. I thought everything was fine until I tested on the server and
realized that Word is not installed on the server (Access is, but only for
the purpose performing some nightly routines).
So, my problem was that I have clients running Office 2000 (10.0), Office
2003 (11.0), and server with only Access installed. I think I can get
around this by putting the required .OLB file on the server and using its
UNC path to refer to it. This seems to work, but when I open the database
and look at things from the 2000 & 2003 clients, and the server, I see
different paths to the Word reference:
2000 Client path shows the exact UNC path I entered for the reference -
because it has no local file to point to?
2003 Client path shows that it is pointed to the local drive for the
reference - becuase it has a local file to point to?
Server path shows that it is resolving the path (\\server\path becomes
D:\folder\subfolder\file) - because it thinks it's smart?
Anyone know if this is a problem or if there is a better way to do this?
Thanks & Ciao
I've got a database into which I have to import data from MS Word. I
initially made a reference to 'Microsoft Word 11.0 Object Library' for this
purpose. I thought everything was fine until I tested on the server and
realized that Word is not installed on the server (Access is, but only for
the purpose performing some nightly routines).
So, my problem was that I have clients running Office 2000 (10.0), Office
2003 (11.0), and server with only Access installed. I think I can get
around this by putting the required .OLB file on the server and using its
UNC path to refer to it. This seems to work, but when I open the database
and look at things from the 2000 & 2003 clients, and the server, I see
different paths to the Word reference:
2000 Client path shows the exact UNC path I entered for the reference -
because it has no local file to point to?
2003 Client path shows that it is pointed to the local drive for the
reference - becuase it has a local file to point to?
Server path shows that it is resolving the path (\\server\path becomes
D:\folder\subfolder\file) - because it thinks it's smart?
Anyone know if this is a problem or if there is a better way to do this?
Thanks & Ciao