Mail Merge Opens 2nd Copy of Database

[lstocky]

I'm trying to automate a mail-merge operation as best as possible from Access.

I've set up a mail-merge ready document which has a paramerterised query as it's datasource which is in a database called Wuk10.mdb. The queries parameters are all set at run-time.
Frustratingly the document insists on opening a second instance of Access (Wuk10.mdb) up rather than using the already open copy to get its data from. This not only makes the process untidy but means that the query shows no records because the parameters have not been set in the second instance of the database.

This causes an error as might be expected. Is there a way of ensuring that the instance which the user has called the mail-merge from is the one which document uses for it's source?

thanks for any help in advance.
lstocky

[lstocky]

this is a really frustrating problem - has anyone had any experience with mail merge out there? How have you gone about it or are your requirements different from mine?

I'm attempting to use mail merge for the creation of letters per case on our system. Before using mail merge I had written a large and cumbersome procedure which formulated the letters using bookmarks. But it was very buggy and slow, mail merge ought to be a faster & more efficient solution but it's just a pain it plays up like this.

anyone going to help me out here?