OK, I managed to check some things on a WordXP system again. Can you try the
same as before, but use

wdMergeSubtypeWord2000 instead of wdMergeSubtypeOther

?

(That's what I thought it should be under Word 2002 but it didn't seem to
work under Word 2003)

Another ODBC is to create a file DSN and use that to access the file. You
can create a file DSN in the ODBC Administrator we looked at earlier, but
you can also do it in Wordpad as long as you know the exact name of the
Driver (it's the name that appears in the list when you create a new DSN in
ODBC).


For example, create the following file in Notepad and save it as
c:\filedsns\mydsn.dsn

[ODBC]
DRIVER=Microsoft Text Driver (*.txt; *.csv)
PageTimeout=5
MaxBufferSize=2048
FIL=text
DriverID=27

Then use this code:

..OpenDataSource _
Name:="c:\filedsns\mydsn.dsn", _
Connection:="FILEDSN=c:\filedsns\mydsn.dsn;", _
SQLStatement:="SELECT * FROM ktext.text", _
SubType:=wsMergeSubTypeWord2000


That's my last attempt for tonight!

Peter Jamieson
"bilisa" wrote in message
...
I tried with your suggestions, but same result.. hope we can crack this one


"Peter Jamieson" wrote:

Sorry, my mistake. I still think it can be done, but right now I can only
check with Word 2003, which sometimes behaves in a slightly different
way.
Apologies in advance if neither of these suggestions work:

ActiveDocument.MailMerge.OpenDataSource
Name:="", _
Connection:="DSN=Delimited Text
Files;DBQ=C:\;DriverId=27;FIL=text;MaxBufferSize=2 048;PageTimeout=5;", _
SQLStatement:="SELECT * FROM " & filnavn, _
SubType:=wdMergeSubTypeOther

or perhaps just

ActiveDocument.MailMerge.OpenDataSource
Name:="", _
Connection:="DSN=Delimited Text
Files;DBQ=C:\;DriverId=27;FIL=text;MaxBufferSize=2 048;PageTimeout=5;", _
SQLStatement:="SELECT * FROM " & filnavn

It is certainly a conversion problem, but
a. if you try to open the file as a "text file" (you can see a bit more
of
what is going on if you check Word Tools|Options|General|Confirm
conversion
at open before opening the file manually) you will probably see the
oriental
characters or a dialog asking about the character set
b. if you try to use OLEDB, usually you see a dialog asking for the text
(field) delimiter, and you may also see a character encoding dialog

Peter Jamieson


"bilisa" wrote in message
news
I followed your instructions, but I still have the same problem. It
seems
to
me that this is some sort of conversion problem. Any ideas?

"bilisa" wrote:

This may sound as a stupid question: What is Text Driver DSN on
system?

"Peter Jamieson" wrote:

I suggest you try the following instead, but use the pathname of the
folder
containing your text file instead of "c:\myfiles", and if necessary,
change
the name of the ODBC DSN in the connection parameter to match the
name
of a
Text Driver DSN on your system.

.OpenDataSource _
Name:=filnavn, _
Connection:="DSN=Delimited Text
Files;DBQ=c:\myfiles;DriverId=27;FIL=text;MaxBuffe rSize=2048;PageTimeout=5;",
_
SQLStatement:="SELECT * FROM " & filnavn

Peter Jamieson

"bilisa" wrote in message
...
Hi

Im having problems when I merge my document / template with a .csv
data
source. My data source is already attached to the template via
some
vba
script. I have some translation problems when the data posts
contain
danish
letters as Ø,ø,æ,Æ,å, Å. Some times they disappear and sometimes
they
turn
into asian symbols in the merged letter. They open correctly in
Excel
but
are
not displayed correctly in the merged letter.

This is my code:

Dim myheader As String

filnavn = "C:\FLETFIL.CSV"

With ActiveDocument.MailMerge

.MainDocumentType = wdFormLetters

.OpenDataSource _
Name:=filnavn, _
Connection:="Entire Spreadsheet", _
SubType:=wdMergeSubTypeWord2000

' Do it
.Destination = wdSendToNewDocument
.Execute
End With

What is wrong with it? Any help is appreciated.

Yours sincerely