[Roger Bunch]

I am using Word 2002 with SP3 and have a Customer ID alphanumeric merged
field which is populated using HTML as the data source. This field works fine
with one exception. If the next to the last character is the letter D then I
get strange results. For example, 309181618D1 becomes 3091816180, 309181618D4
becomes 3091816180000, 309181618D8 becomes 309181618E+16, etc. Changing the
Customer ID is not an option. Any suggestions?

[Peter Jamieson]

Weird. This can happen if Word 2002/3 uses OLEDB to open the HTML file. If
it is doing that, you will probably have to pick a table from a list when
you try to connect to the data source.

However OLEDB isn't Word's default method for connecting to HTML files, so
I'd have to guess that you also have Word Tools|Options|General|"Confirm
conversion at open" checked and are choosing the OLEDB option.

Either way, ensure that option is checked, select either of the options that
doesn't say "OLEDB", and the problem should disappear.

(FWIW I don't know why the OLEDB HTML provider (which is part of the
Access/Jet database engine) interprets the value in this way, but perhaps
there's a good reason)

Peter Jamieson

"Roger Bunch" Roger wrote in message
...
I am using Word 2002 with SP3 and have a Customer ID alphanumeric merged
field which is populated using HTML as the data source. This field works
fine
with one exception. If the next to the last character is the letter D then
I
get strange results. For example, 309181618D1 becomes 3091816180,
309181618D4
becomes 3091816180000, 309181618D8 becomes 309181618E+16, etc. Changing
the
Customer ID is not an option. Any suggestions?

[Roger Bunch]

That seems to have been it. Thanks.

"Peter Jamieson" wrote:

Weird. This can happen if Word 2002/3 uses OLEDB to open the HTML file. If
it is doing that, you will probably have to pick a table from a list when
you try to connect to the data source.

However OLEDB isn't Word's default method for connecting to HTML files, so
I'd have to guess that you also have Word Tools|Options|General|"Confirm
conversion at open" checked and are choosing the OLEDB option.

Either way, ensure that option is checked, select either of the options that
doesn't say "OLEDB", and the problem should disappear.

(FWIW I don't know why the OLEDB HTML provider (which is part of the
Access/Jet database engine) interprets the value in this way, but perhaps
there's a good reason)

Peter Jamieson

"Roger Bunch" Roger wrote in message
...
I am using Word 2002 with SP3 and have a Customer ID alphanumeric merged
field which is populated using HTML as the data source. This field works
fine
with one exception. If the next to the last character is the letter D then
I
get strange results. For example, 309181618D1 becomes 3091816180,
309181618D4
becomes 3091816180000, 309181618D8 becomes 309181618E+16, etc. Changing
the
Customer ID is not an option. Any suggestions?