Have posted this query to a Word newsgroup and from the replies I'm getting
it appears to be a bug with Word 2002. In case anyone out there gets a
similar problem and is interested the following website aricle may shed some
light.
http://homepage.swissonline.ch/cindy...r/MergFram.htm
Click the link for Merge in Word 2002 and then select link Numeric and date
formatting under Connection Methods article.
Thanks for all the help everyone and I'll keep you posted how it goes.
Dawn
"Justin Hoffman" <j@b.com> wrote in message
news:d98a1l$8n$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...[color=blue]
> "Andy Davis" <ad_davis@westnet.com.au> wrote in message
> news:42b75dea$1@quokka.wn.com.au...[color=green]
>> Justin
>>
>> Many thanks but have already tried this but still did not work.
>>
>> Dawn
>>
>> "Justin Hoffman" <j@b.com> wrote in message
>> news:d96lg6$7g0$1@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com...[color=darkred]
>>> "Andy Davis" <ad_davis@westnet.com.au> wrote in message
>>> news:42b6d41b$1@quokka.wn.com.au...
>>>> Thanks for that. Have already set the date format in the query but no
>>>> change.
>>>>
>>>> Thanks again
>>>>
>>>> "Rog" <roger_delahaye@hotmail.com> wrote in message
>>>> news:1119277393.941615.209280@g49g2000cwa.googlegr oups.com...
>>>>> Could it be one of the pc's has a different regional setting? Try
>>>>> formatting the dates the way you want them in a query and use that as
>>>>> your source.
>>>
>>> You can force Word to use your preferred date format by using what Word
>>> calls 'field switches' and are set up from the Word document or
>>> template.
>>> You can get full details from the help file but in your case you simply
>>> need
>>> to make sure your merge field says something like: { MERGEFIELD MyDate
>>> \@
>>> "dd/MM/yyyy" }
>>>
>>> Note you must use capital M for month - lower case m is for minute.[/color][/color]
>
>
>
> I have never seen the MS Word field switches overridden - whenever date or
> currency issues have occurred between machines, I have found this to work.
> When you say you tried it, you mean that it worked on your machine but not
> on your client's? Did you do this personally on site or just receive
> feedback from the client?
> The only things that occur to me are:
> Make sure the field in Access is a real date field (not for example a text
> field where someone is filling in a date) Perhaps you could check the
> client's dataset.
> Make sure you avoid reserved words like 'name' and 'date' for field names.
> It may be worthwhile getting the client to check his references and make
> sure none are missing.
> If this is still a problem, you could go through the Windows control panel
> settings with your client and try and replicate the problem.
>
>
>[/color]