Date mergefield problem!

D

Damon

Hi,

When using date switch in Word 2002 i.e. @ "MMMM yyyy" on a Windows XP
machine it prints out as required e.g. April 2003, however when printing the
exact same document on a Windows NT machine it prints out as January 2003,
which I gather means it is taking it as American format instead of UK. I
have checked the regional setting on the Windows NT machine and they are set
to UK but still prints out as January 2003. Any ideas on this really
frustrating problem would be greatly appreciated.

Thanks

Damon
 
G

Graham Mayor

What are you trying to say here? That America is a few months behind? ;)

The date switch you have illustrated should produce the month - spelled out
in full, followed by the year as four digits. The regional settings
shouldn't affect this.

If the field is producing a different date altogether ie January instead of
April, then the field or the data it refers to is the problem rather than
the switch (which is working correctly) where is the field getting its
information from and what is the rest of the field?


--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
 
D

Damon

Hi,

Thanks for replying. The data source is an Excel 2002 spreadsheet, when I
view the data in there it is laid out as 01/04/2004, this should then go
into Word using my switch as APRIL 2004 which it does when using my Windows
XP machine but goes in as JANUARY 2004 when using the Windows NT machine.
It's obviously nothing to do with the data source other wise I would have
the same problem on the XP machine. Is certainly a stange one. Appreciate
any advice.

Thanks

Damon
 
P

Peter Jamieson

This is probably down to an error in the OLEDB provider for Excel, which is
what Word 2002 will be using to connect to Excel unless you deliberately
connected using DDE, ODBC, or the Excel converter The problem has been
around for a while. See

http://support.microsoft.com/default.aspx?scid=kb;en-us;327579

As for why Word behaves differently on NT and XP, I don't know, but maybe
a. you have installed the relevant SP on one machine but not the other or
b. there are different versions of the OLEDB provider on the two machines
and one works, one doesn't.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top