Mail merge opening another copy of database

[Rusty]

Hey Guys,

Hope you can help as this one's got me stumped!

I'm using Access 2000 and run a mailmerge function via a button on a form. (It opens Word, which then uses a query in the database to refer to and then 'automerges' into a new Word document).

It used to work absolutely fine but now it opens Word and then opens another copy of the database (so I have 2 running) and all hell breaks loose.

Any ideas what I can do to stop this? Has anyone come across this before?

Any help/suggestions would be gratefully recieved as I feel like I'm in a 'needle in a haystack of needles' situation here.

Cheers,

Rusty

 

[Pat Hartman]

I used to know the answer to this because I ran into the same problem. As I recall, it has something to do with the way the mailmerge is set up and whether the DDS option is chosen. I don't have time to try to reconstruct the solution but I think I originally found the answer in the MS knowledgebase.

 

[Rusty]

Thanks Pat.

I went for the 'quick and dirty' fix and created a blank database and imported all the objects from the original.

I then deleted the original and renamed the 'fix' version and hay presto it works fine and the problem no longer occurs.

Wierd huh?

Thanks for your help - I shall read up on the DDE stuff in case this happens again.

Rusty