Empty fields

Hello,

I have a MySQL ODBC data source which simply retrieves one column of a
table. If this column has the "latin1_swedish_ci" charset, everything works
fine. If I switch to "latin1_german1_ci" Word retrieves the correct number
of rows but each and every field is blank. The strange thing is, that if I
edit the data source via Microsoft Query even with "latin1_german1_ci"
charset everything is being displayed - only Word (2007) itself does not
show the text. Any ideas?

Regards
Christoph Kling

OK, update:

excel (2007) always displays the correct data no matter what collation (not
charset, sorry) is set.

Regards,
Christoph Kling



"Christoph Kling" schrieb im Newsbeitrag
...
Hello,

I have a MySQL ODBC data source which simply retrieves one column of a
table. If this column has the "latin1_swedish_ci" charset, everything
works fine. If I switch to "latin1_german1_ci" Word retrieves the correct
number of rows but each and every field is blank. The strange thing is,
that if I edit the data source via Microsoft Query even with
"latin1_german1_ci" charset everything is being displayed - only Word
(2007) itself does not show the text. Any ideas?

Regards
Christoph Kling

I can't check here, now, but
a. "latin1_swedish_ci" is the /default/ collation
b. http://dev.mysql.com/doc/refman/5.1/...onnection.html
suggests that there may be various settings that might result in some
conversions when MySQL returns values to other applications
c. could using a non-default collation trigger such a conversion?
d. if the result of such a conversion was to provide any form of
Unicode encoding (UTF-8 or otherwise) then I am pretty sure that Word
would not see the resulting values via an ODBC interface. AFAIK this is
specifically a fault in either Word or in the wretched ODSO object that
Word relies on to get its data, which might just about explain why it
all looks OK in MS Query and Excel, but not Word.
e. Is there still a usable MySQL OLE DB provider? If so, it may be
worth trying that. But I had the impression that that was
"de-emphasised" a few years ago.

Peter Jamieson

http://tips.pjmsn.me.uk

Christoph Kling wrote:
OK, update:

excel (2007) always displays the correct data no matter what collation (not
charset, sorry) is set.

Regards,
Christoph Kling



"Christoph Kling" schrieb im Newsbeitrag
...
Hello,

I have a MySQL ODBC data source which simply retrieves one column of a
table. If this column has the "latin1_swedish_ci" charset, everything
works fine. If I switch to "latin1_german1_ci" Word retrieves the correct
number of rows but each and every field is blank. The strange thing is,
that if I edit the data source via Microsoft Query even with
"latin1_german1_ci" charset everything is being displayed - only Word
(2007) itself does not show the text. Any ideas?

Regards
Christoph Kling