Hi Brenda,
I don't have anything to add to the excellent info from the respondents. However, I believe it may be best to get you mail merge data into a format less susceptible to OBDC issues. See: http://www.officevba.com/features/2000/10/vba200010cm_f/vba200010cm_f.asp

I'm just testing this.
Instead of
COPY TO DataSource TYPE FOX2X
do a
COPY TO Datasource.CWH TYPE CSV
Then hook up your datasource to the mailmerge object as Gary mentions. Using CWH (my made up Commas with Header extention that has no OBDC meaing) should ensure that Word uses its internal text converter, not OBDC.


>I have several mailmerge documents that are linked to .dbf free tables. I want code that determines the link is to a *.dbf, then breaks the link while preserving the document with its' mergefields and then I would do a DO CreateDataSource to reestablish the link to a word doc that has the data in a word table. I have the Hentzenwerke book on Office Automation and am using that as a base. But it works with templates and new documents. I can have new documents as my clients can create new ones, but I also have existing documents that I no longer want to have linked to .dbfs. Also do not want to use templates because then my client can not so easily make changes to the main document.
>
>Thanks
>
>Brenda