Hi Pip""n
<<
> How do I rebuild the data source so that it doens't reference a connection
> that is stored on the host machine?
AFAIK, the DATABASE field expexts to find the "data source" somewhere in the
Windows file system.
e.g., if you copy your .odc file to a network folder that can be accessed
via a UNC pathname or a driveletterx:\pathname you should still be able to
use your DATABASE field. The .odc should describe the /source database/ in a
way that is not relative to the location of the .odc itself.
If you can't do that, there is no alternative AFAIK, because you can't point
to a SQL without a .udl, .odc, or old-style .dsn (for ODBC connections) and
in the case of ODBC, you must at least have the ODBC driver on the machine,
and a suitable ODBC DSN or .dsn file.
Peter Jamieson
>I have a merge document that is located on a server that is accessed using
>a
[quoted text clipped - 16 lines]
> The name of the data source in this case is "MyIntranet
> mailMerge_Service.odc".
Pip''''n - 04 Aug 2007 00:32 GMT
That first solution was exactly what I did. Glad to see that my intuition was
following the right thought process.
Thanks for your help Peter.
> Hi Pip""n
>
[quoted text clipped - 37 lines]
> > The name of the data source in this case is "MyIntranet
> > mailMerge_Service.odc".