Mark Breen
marklbreen at gmail.com
Sat Apr 3 06:53:51 CDT 2010
Hello All, I think that the following works perfectly as a solution for my problem posted below. http://support.microsoft.com/kb/214183 <http://support.microsoft.com/kb/214183>if you need this, review it carefully, as I missed out the critical bit in the Word 2007 section where it refers you to the Options button first. Incidentally, in my Word 2003, I also had to go to Options\general to turn on the DDE access. If tech and sql are seeing this for the first time, it is because I mis typed the email on the first pass, so now you get a solution to a problem you did not have ! :) Thanks Mark On 3 April 2010 11:50, Mark Breen <marklbreen at gmail.com> wrote: > Hello All, > > First of all, I hope you are not annoyed by my three cross posts. This > question involves MS Word mailmerges, MS Access and MS SQL Server. > > I have a SQL Server database hosting in a data centre. > I have an Access 2003 db with ODBC inked tables to the SQL Server > I have a query with hard coded Criteria -- eg Where CustId = 100 > I have MS Word Version 2003 with a MailMerge doc Set up and connected to > the Query in MS Access. > The Mailmerge works well with this setup > > When I change the above setup to use parmeters instead of hard coded values > in the criteria of the query, I can successfully run the query from within > access. The params popup and ask for the param value, and then the query > executes and returns records as expected. > > However, the MS Word mailmerge does not work, and the mailmerge doc cannot > connect to the data source. If I try to re-establish the data source > connection, MS Word does not even see the query as a potential data source > within the db. > > If you have any suggestions, I would really appreciate it. > > Thank you, as always for your time, > > Mark > > >