Using ODBC or OLE DB, there is a problem if the data types in a column are
mixed (this is described in that t0003.htm page I mentioned).
If you have control over the content of the Excel sheet, can I suggest that
you try the Data|Text to columns approach for the offending date columns (or
all of them), or at the very least, /type/the very first date in each date
column using some non-numeric text (e.g. 14 Feb 2008). I am not sure that
will actually help in this case but right now I'm a bit strapped for time,
and it might just be enough to sort this out. Otherwise, let me know as I
have made a bit of progress on that t0003.htm article since I last updated
it.

Signature
Peter Jamieson
http://tips.pjmsn.me.uk
> (BIG SIGH...)
>
[quoted text clipped - 42 lines]
>> > This one is showing up as "2/10/2008"
>> > {MERGEFIELD "ACTUAL_SURVEY_DATE" \@ "dd MMM yyyy" }
Suzanne - 20 Feb 2008 19:53 GMT
It doesn't seem the Word or Excel MVP's can figure this one out. It appears
its just another goofy thing Word does.
The work around was to change the Excel date columns to 'Custom: ##-##-####'
(to get 02-20-2008). I obviously am not querying off any of the date fields,
otherwise this might still be a problem.
Thanks for your help (esp Peter). I think I'm finally finished with the
Excel workbook and Word merge forms.
Suz
> Using ODBC or OLE DB, there is a problem if the data types in a column are
> mixed (this is described in that t0003.htm page I mentioned).
[quoted text clipped - 54 lines]
> >> > This one is showing up as "2/10/2008"
> >> > {MERGEFIELD "ACTUAL_SURVEY_DATE" \@ "dd MMM yyyy" }
Peter Jamieson - 21 Feb 2008 08:48 GMT
> I think I'm finally finished with the
> Excel workbook and Word merge forms.
That must be a relief!

Signature
Peter Jamieson
http://tips.pjmsn.me.uk
> It doesn't seem the Word or Excel MVP's can figure this one out. It
> appears
[quoted text clipped - 82 lines]
>> >> > This one is showing up as "2/10/2008"
>> >> > {MERGEFIELD "ACTUAL_SURVEY_DATE" \@ "dd MMM yyyy" }