Thank you for taking the time to respond. If I understand correctly, the
main document saves the merge fields but the data itself is not saved. The
recipient will need to have access to the data source as well.
You probably got it. But just to clarify, in case...
The mail merge main document does contain information about the data source,
and it also tries to remember which record you were previewing in the data
source when you saved the document. But that information is essentially to
do with the data source that /your/ machine sees. If, for example, it is an
Access database at c:\mydbs\mydb.mdb, when they open the document, Word will
try to connect to \their\ c:mydbs\mydb.mdb, which might be a completely
different database with different tables, fields and data. So...
> The
> recipient will need to have access to the data source as well.
The recipient needs access to the data source that they need to complete the
merge. If every recipient needs the same data, you either have to provide
access to the same central data, or you have to provide copies of the same
data to each recipient. If the point is that each recipient is using the
same data structures (same tables etc.) but has dffierent data in their
local database, all you really need to be concerned about is that the merge
document either works when each recipient opens it, or that each recipient
knows how to connect the document to their own local data.
Peter Jamieson
> Thank you for taking the time to respond. If I understand correctly, the
> main document saves the merge fields but the data itself is not saved. The
[quoted text clipped - 32 lines]
>> > SQL
>> > command to a source (i.e. database or Excel file).
TedRusky - 13 Jul 2005 22:11 GMT
Thank you!
> You probably got it. But just to clarify, in case...
>
[quoted text clipped - 56 lines]
> >> > SQL
> >> > command to a source (i.e. database or Excel file).