To see the option you have to check Word Tools|Options|General|Confirm
conversions at open. Then you get the same "Confirm" dialog after you select
the .mdb.
Peter Jamieson
>I am also using an Access 97 database as the data source for a Word mail
> merge. The data originally comes from SQL tables using ODBC links. This
[quoted text clipped - 6 lines]
> select a
> DDE link instead of ODBC.
In Word 97/2000, DDE was the default connection method and ODBC was the
alternative as far as Access/Jet sources were concerned.
In Word 2003, OLE DB is the default, but unfortunately when you have
selected your database, Word does not display the Access tables that are
linked to ODBC data sources (which is what you would have even if your
Access database is Access 2000 format or later). It isn't that OLE DB cannot
"see" the tables: it can, but Word seems to ignore them.
So what can you do? Well, assuming there are no additional problems related
to the fact that it's an Access 97 format database rather than (say) Access
2000 format, you can
a. check Word Tools|Options|General|Confirm conversions at open, go through
the connection process again, and select either a DDE or ODBC connection
from the additional dialog box that's displayed. If you chose ODBC, you will
need to check that Word has selected the correct .mdb (it's impossible to
see if the pathname is long), click Options... then select all the boxes.
You should see the list of linked tables. Or
b. create one query in your Access database for each linked table you want
to use, with SELECT * FROM [thattablename], and use that as the data source
(which I think you are probably already doing). Or
c. connect using Word VBA and the OpenDataSource method. All you really
need in this case is
Sub ConnectToAccess()
ActiveDocument.MailMerge.OpenDataSource _
Name:="the full path name of your .mdb", _
SQLStatement:= "SELECT * FROM [theAccesstablename]"
End Sub
or
d. create a .odc file for each linked table and use those when you select
your data source. (in Word's "Select Data Source" dialog box
- click New Source
- Other/Advanced
- select the Microsoft Jet 4.0 OLE DB Provider. Click "Next"
- enter the full path name of the .mdb. Click Yes (test the connection
if you want)
- you should then see a list of tables. Select the one you want, then
name and save the .odc file
- Word then prompts for a data source - select the .odc you just
created, and select the OLE DB Databases connection method if word prompts
you for that.
or
e. connect directly to your SQL database (typically you also have to create
a .odc for that cf. point (d) above, but using the appropriate provider
instead of the Microsoft Jet one.
The different ways of connecting have their advantages and disadvatages so
find out whether there are any importnat things you cannot do (e.g. you
might not be able to sort/filter or edit data source records in Word, and so
on).

Signature
Peter Jamieson
http://tips.pjmsn.me.uk
>I am also using an Access 97 database as the data source for a Word mail
> merge. The data originally comes from SQL tables using ODBC links. This
[quoted text clipped - 6 lines]
> select a
> DDE link instead of ODBC.
Sharon L. - 25 Oct 2007 20:13 GMT
Thank you for so much your response Peter. Changing the Word setting allowed
the DDE connection to be selected so the queries worked just like they did in
Word 2000. (The other part that you mentioned isn't practical as there are
many different databases, tables and word documents used in the merges so
there is too much work involved in trying to fix it all). That alone solved
the problem but brought up another issue.
The situation is that some staff are using Word 2000, others are using Word
2003 and I am now starting to test Word 2007. If someone creates a new mail
merge and uses ODBC, what happens to those who try to run it in Word 2000?
Should they stick to DDE instead? People are using these database queries and
merges to get work done and really won't want to spend all their time redoing
everyhing that used to work properly.
Normally we upgrade computers and software for 1/3 of the staff each year.
This is why we are using different versions. We are still using Access 97
because the format change in Access 2000 and 2002 didn't work properly. (VBA
code didn't run etc).
Are there any resource materials that you know of that discuss these issues
and suggest an approach to upgrading the different versions of Office? For
example, If we all went to Office 2007 including Word and Access at the same
time, is there an easy way to keep what used to work in Access 97 and Word
2000 working without an incredible amount of reconstruction?