Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- From: Jolyon Cox <JolyonCox@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 21 May 2007 02:48:01 -0700
Thanks for the reply. In answer to your points:
1) We are using the Word 2000 automation interface because that is what is
supported by the tool in which the programs are developed (Borland Developer
Studio 2006). In this version, for instance, the OpenDataSource() method has
only 14 parameters rather than the current 16. However, we actually have
Office 2003 installed because this fixes some (though not all) other problems
to do with mail-merge.
2) I tried adding the registry key mentioned in the KB article - for Word 11
as well as Word 10 - but it makes no difference.
3) I don't think your suggestion for using .odc is feasible - the items in
the data source come from a variety of places. Many of them are retrieved
from an Ingres database via ODBC, but some are created on the fly by
application code. Anyway, I do not have the resources to rewrite and re-test
all the affected applications, not to mention retraining all the developers.
All I am trying to do is prevent Word from making wild (and wrong) guesses
about the content of a mail-merge data source - surely this is not an
unreasonable thing to expect ? I do note that even the latest implementation
of OpenDataSource() does not have an encoding parameter as Documents.Open()
has - this seems to be the real problem.
I will keep plugging away and let you know of any progress...
Jolyon
"Peter Jamieson" wrote:
BTW, to use the .odc sample I reference, you will probably need to replace
the reference to the ACE OLE DB provider in the connection string by the Jet
one, i.e. replace
Microsoft.ACE.OLEDB.12.0
with
Microsoft.Jet.OLEDB.4.0
Peter Jamieson
"Peter Jamieson" <pjj@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:62539979-0D48-4CF1-BDB1-DD190DC6E389@xxxxxxxxxxxxxxxx
Is it Word 2000, as you first mention, or Word 2003? From your description
it sounds like 2003, but there are significant differences.
It is probably worth seeing if setting the DefaultCPG registry value
described in
http://support.microsoft.com/kb/290981/en-us
(It's also possible that opening the document in Word with an explicit
encoding , saving it as a WOrd document, then using that as the data
source for a merge, as described in that article, might do the trick).
If your data source has 255 columns or fewer, and you are using Word 2003,
you can try the approach using .odc and SCHEMA.INI that I described in the
conversation beginning at
http://groups.google.com/group/microsoft.public.word.mailmerge.fields/browse_thread/thread/dc1076d59b977c64/d39588c43fc31d70?lnk=st&q=jamieson+SCHEMA.INI+odc+text+unicode&rnum=1
If you are using Word 2000, that can't work because it doesn't support OLE
DB and .odc files. Although you can use ODBC to connect using a similar
SCHEMA.INI, the ODBC driver does not seem to recognise all the entries in
the .INI file that the OLE DB provider does, and it doesn't have the same
character encoding support anyway AFAIK.
In this particular case, it's possible that the 8-bit encoding will screw
up any encoding choices you make anyway, if Word does recoognise the
characters as being part of the character set implicitly or explicity
specified. However, you can but try.
Peter Jamieson
.
- Follow-Ups:
- Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- From: Peter Jamieson
- Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- References:
- Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- From: Peter Jamieson
- Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- From: Peter Jamieson
- Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- Prev by Date: Re: DDE Access to Word using mde
- Next by Date: Merge & Link Fields update correctly in Word 2000, BUT not in Word 2002. HELP !!!
- Previous by thread: Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- Next by thread: Re: How do I tell Word 2003 my mail-merge text is NOT UTF-8?
- Index(es):
Relevant Pages
|
