Thanks Doug,
However, on my colleague's computer, the fields are showing 0s and not 12. I
guess I was not clear in my original message.
The value in the fields are 0s. For example, the values in the fields
"Contributions" are 0,00 for all except records 43, 56 and 61. In Word, I
have the following:
{ IF { MERGEFIELD "Contributions" } = 0 "" { MERGEFIELD "Contributions" \#
"# ##0,00}"}
When I'm merging I get 12s. My colleague get nothing which is what I want. I
already verify all
the Control Panel Regionnal Settings and they are the same.
Also, I have the following problem (found on the MVP Word site) :
Dates: day/month reversed
On Windows installations where the short date format in the Regional
settings is not the North American standard month/day/year, Excel and Access
users will find that, in cases where the day is 12 or less, the month and
day will come across the link reversed.
This is a bug; and comes from the OLEDB driver Microsoft provides for these
two applications. Not only Word Mail merge users struggle with this
problem - it also affects database programmers.
In this case, simply adding a formatting switch to the merge fields will not
resolve the problem.
You have two choices: The data will have to be pre-formatted, as text, as
described in the general Mail merge section; or use a DDE or ODBC
connection.
Again, my colleague can do the all the same operations as me but without
having this problem. She open the same word merge document and connect to
the same CSV data source thru OLE DB and don't get the problems that I get
(12s showing every where values a 0 and day/month reversed dates).
Can I update my OLE DB driver ? Could it be the my colleague has more up to
date OLE DB drivers ? How and wher can I verify which version of the OLE DB
drivers I'm using ?
Thanks again
Jean-Philippe
"Doug Robbins - Word MVP" a écrit dans le message
de news:
...
For the problem fields, the data in the first records(s) must be being
detected by Word as Date fields an on your colleague's computer, the
Control Panel Date format is probably set to not include the time in
addition to the date.
The switch should be \@ "hh:MM:ss AM/PM" to get 12:00:00 AM
--
Hope this helps.
Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.
Doug Robbins - Word MVP, originally posted via msnews.microsoft.com
"JPGaudreau" wrote in message
...
Hi,
I have an Access database which contains my raw data. With C#, I'm doing
a lots of calculations on these data.
I'm exporting these calculated data into a CSV file. But before exporting
these data I'm formatting them (in the language required for each
record). Once my calculated data have been exported, I doing a mailmerge
with Word 2003. I'm using CSV because it's also easy to open it with
Excel.
If I select OLE DB data source, I have a screen popping up twice which
ask me to choose the type of separated value. Once the merge is done, I
have the bug that all the 0s in my data source file are 12:00:00 AM !
However, I did the same thing with same Word mailmerge file and the same
data source on a colleague's computer and I do not have this "bug". Also
when I'm switching of records, it's really fast compared to the 2 other
data connections I tried.
If I'm trying to format the mergefield in word (\# #,##0.00), I'm getting
the value 12 instead of 12:00:00 AM.
Also, when I'm doing the merge with the data source DDE or Text files,
I'm not getting this bug. However, like I said it's really slower than
with OLE DB.
Is that could a be driver problem ?
I'm also using CSV because all the data is preformatted and the CSV
format is a text format so I could use the OLE DB data connection and be
much more faster* ...
Anybody could help me please ?
Thanks
Jean-Philippe