Hi Cindy,

Sorry, I should have started by saying I'm rolling my own mail merge
here within a Word macro.

The data source is an XML file created via VB6/ADO from an Access 2000
database. In the test case, it contains just a single record. The Word
macro opens this file and replaces each MERGEFIELD in the new document
with the value of the named field.

And yes, if I strip it all down to just the AreaCode1 field, the new
document is empty.

All that I can think of is that some new DLL is causing a screw-up in
the evaluation of Word "IF condition true-output false-output" fields
when they're nested, but that seems so unlikely. Or at least unlikely
to have gone unnoticed.

BTW, here are the contents of a sample XML file:

xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
xmlns:rs='urn:schemas-microsoft-com:rowset'
xmlns:z='#RowsetSchema'
s:Schema id='RowsetSchema'
s:ElementType name='row' content='eltOnly' rs:updatable='true'
s:AttributeType name='AreaCode1' rs:number='19' rs:nullable='true'
rs:maydefer='true' rs:write='true' rs:basetable='Address'
rs:basecolumn='AreaCode1'
s:datatype dt:type='string' dt:maxLength='4'/
/s:AttributeType
s:AttributeType name='Phone1' rs:number='20' rs:nullable='true'
rs:maydefer='true' rs:write='true' rs:basetable='Address'
rs:basecolumn='Phone1'
s:datatype dt:type='string' dt:maxLength='36'/
/s:AttributeType
s:AttributeType name='Type1' rs:number='18' rs:nullable='true'
rs:maydefer='true' rs:write='true' rs:basetable='Address'
rs:basecolumn='Type1'
s:datatype dt:type='string' dt:maxLength='10'/
/s:AttributeType
s:extends type='rs:rowbase'/
/s:ElementType
/s:Schema
rs:data
z:row AreaCode1='701' Phone1='333-2398' Type1='Phone'/
/rs:data
/xml