Hi Dominic,
When picking up a text file in Word 2000 (note _2000_, not 2002 or 2003 -
this is important!), Word has the choice of using ODBC or its internal text
converter. Given your macro code, I'd assume Word will try to use the text
converter (you don't specify a DSN or anything of that sort). That should
be present on every machine and not cause a problem. OTOH, I don't know
anything about metaframe, either, so I don't know how/whether it might be
interfering.
The first thing I'd test, is whether this file can be opened in the UI. If
it can, then someone should record a macro while doing so, so that you can
compare the OpenDataSource code and see what kind of connection Word
"wants" to use.
My personal feeling is that this metaframe may somehow be blocking Word's
access to the external file.
> 'Set object reference to this mail merge (convenience coding)
> Set thisMerge = ThisDocument.MailMerge
[quoted text clipped - 14 lines]
> settings or something. I know little about metaframe but our engineer
> says that the user can see C:\Temp\batchmerge.csv.
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)
Dominic Godin - 27 Aug 2004 16:38 GMT
Thanks for the reply.
I managed to fix it in the end. Apparently Word has some nasty bugs
with certain versions of the ODBC. I switched the file extension from
csv to dat so word wouldn't use the ODBC and now all works fine.
Thanks
Dominic Godin
> Hi Dominic,
>
[quoted text clipped - 40 lines]
> This reply is posted in the Newsgroup; please post any follow question
> or reply in the newsgroup and not by e-mail :-)
Cindy M -WordMVP- - 31 Aug 2004 17:43 GMT
Hi Dominic,
> I managed to fix it in the end. Apparently Word has some nasty bugs
> with certain versions of the ODBC. I switched the file extension from
> csv to dat so word wouldn't use the ODBC and now all works fine.
OK, thanks for letting me know. From your code, it didn't look like Word
was making an ODBC connection (no DSN mentioned), which is why I didn't
follow that track.
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)