Too many queries in Microsoft Access to perform a Merge with MS Wo

[TD]

I have developed a database in Access 2000 which has been working fine for
years - now I've moved on to Access 2003 mailmerges have stopped working.
I have read and tried the posts on this board and on the Microsoft Support
web site (and loads of others too) - none of which resolved the problem.
When I try to link a Microsoft Word 2003 document to a Query (or even a
table) in Access 2003 using "MS Access databases via DDE", I get the message:
"Word could not establish a DDE connection to Microsoft Access to complete
the current task" before you get the chance to choose a Table or Query to
link to.
I have to use DDE as many of the queries are parameter queries (so ODBC and
OLE DB won't work for that - I think). The settings in Word are fine for
Confirm Conversions on Open and the database is not open in exclusive mode.
After hours of trying different things, I have found that deleting 70 or so
Queries from my database (of approximately 600 queries) makes everything
works fine. Any 70 or so queries being deleted is fine - it doesn't matter
which ones (so it probably isn't a corruption in a query).
I have over 200 forms - the number of these makes no difference. I have
nearly 100 reports - no difference either.
I have tried separating the front and back end - no difference. I've ported
it from Access 2000 format to Access 2003 format and still no difference.
Compact & Repair or convertion to MDE makes no difference either. I have
created a blank database and imported all the forms and queries in - still no
change.
Has anyone else come across a similar problem in the past for which they
have found a solution? Worst case scenario I'll have to go back to the
comfort of Access 2000 or find 70 queries I don't need any more

Thanks in anticipation of any guidance! I hope I've posted this in the
right place.

 

[Albert D. Kallal]

My solution is to use my super easy word merge.

If you look at the documentation, you can supple the word template with a
query.

And, there is even sample form that lists queries to select..and then allows
you to select a template....

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

However, I don't see why a2000 works, and the a2003 does not. This sounds
likely some type of setup, or reference problem. Both a2000, and 2003 use
the same vb code, and also the same version of JET. There is little, if any
reason why the a2003 don't work. In fact, a2003 defaults to the a2000 format
also. So, I don't know why this is not working..but, it should.

However, try my system...it works for all of them...

 

[TD]

I like your solution very much - I will try and implement this as a
replacement.

Very impressive indeed - thank you for your assistance!

 

[Guest]

ODBC does work with parameter queries. (david)

 

[Fifth Amendment]

my solution is to just use a database that isn't constantly flaky

SQL Server and / or Acceess Data Projects never have this problem

 

[TD]

Finally the problem was resolved - it took 3 weeks though! The problem was
that there were tables with a colon in the name. It appears that whilst 2000
is quite forgiving in this, 2003 is not.