There are three main ways to try to deal with this:
a. Change the way Word connects to Access to DDE (or possibly ODBC)
b. Detect the specific case where the "date" is 12:00:00 AM and insert
blank instead, e.g.
{ IF "{ MERGEFIELD mydate }" = "12:00:00 AM" "" "{ MERGEFIELD mydate }" }
(where all the {} are the special field code braces you can insert using
ctrl-F9)
c. Define a query in Access with a new field that uses e.g. the format
function to format the date the way you want, and use that query as the
data source for your merge.
I find it difficult to recommend (a) - although it's probably the
quickest solution for a one-off merge, it's probably not a good long
term bet. You can change the connection method in Word 2003 and earlier
by checking Tools->Options->General->Confirm conversions at open, then
going through the connection process again and selecting DDE or ODBC.
(Or in Word 2007, look for the same option in Word Office Button->Word
Options). (b) is probably OK as long as none of your date/times is
/actually/ set to 12:00:00 AM. I'd opt for (c) if you are in a position
to create the query. (If not, you should also be able to issue the same
query as the SQLStatement parameter in a Word VBA OpenDataSource call
As far as I know, nothing you do in the Access field definition will
modify this behaviour.
Peter Jamieson
http://tips.pjmsn.me.uk