If the explanations given here didn't help and you are still looking for a
solution, the problem /may/ be to do with the money type. There is certainly
a similar problem with the "currency" type used in Access/Jet in some
circumstances.

Something worth trying is to use a cast or convert function in a SQL Server
view to change the data type, or if you aren't in a position to do that, you
may be able to issue the necessary Transact-SQL in the SQLStatement
parameter of a Word VBA OpenDataSource call (and there may be other ways to
do it).

Peter Jamieson
wrote in message
oups.com...
So I have a DOC file which mail merges from a SQL Server view. The
source data field is a SQL Server "money" type. It should display as a
dollar and cents value within Word. And it works fine except if there
is just a single non-zero digit to the right of the decimal point in
the raw data. If no formatting fields are supplied in the MergeField,
the data appears as 50.9, or 371.4, as I'd expect. However I've yet to
find a formatting for the mergefield which correctly dipslays the
missing trailing 0. Instead Word seems to combine digits. For instance
if the source data is 371.40, it displays as '375.00'; if the soruce is
50.9, it displays as 59.0 If the raw data has two digits to the right
of the decimal point however, e.g. 549.23, it displays correctly in
Word. I've tried innumerable varieties of format codes (\# $#,###.##,
\# $#,###.#0, \# $#,###.00, \# #,###,##0.00 \# $,0.00 \#$0.00 etc.
etc) with the same results each time. Anyone ever run into this before?
Even better, anyone know a solution? (Word 2003 / SP2 running on
Windows Server 2003, SP1; SQL Server 2000).

= Marchand =