Hi Russell.

Word 2003 on my machine, but it will probably be Word 2000 on the client's.

If you can be sure that the client is using Word 2000, why not just export the dbf to an excel spreadsheet first and use that as the dataSOurce for the mailmerge. That is the way I always do it - precisely becuase of the issues you are having right now < s >. I figure that the office suite of tools will most like always be on speaking terms with one another so that means fewer problems for me.

Just one tiny problem you should be aware of. They changed the way that the office tools handle data with office XP, so if you want your word 2000 mailMerges to keep working with excel data sources, you have to use a different syntax for .MailMerge.OpenDataSource().

I am not sure about what surprises are lurking in Office 2003 < s >.