Yes, it's interesting that these characters, and leading/trailing spaces
survive if you get the data via an ADO Recordset, which suggests that
a. OLEDB passes them through
b. they are are stripped/transformed somewhere in Word's
Mailmerge.DataSource object

Peter Jamieson
"Klaus Linke" wrote in message
...
Perhaps you also should complain to MS. The non-breaking space is defined
in all
the relevant encodings (MS code page 1252, ISO8859-1, Unicode), so there's
really no reason why Office should mess with it.

Greetings,
Klaus