I suspect you will find better help in an Access group as far as security
issues and good practices are concerned, but
a. Word 2000 probably tries to start the program associates with .mdb files
(probably the most recently installed version of Access, or the version that
has most recently updated the registry with its file associations (more
likely to be Access 2000). I doubt if it chooses an msaccess.exe depending
on the version of the actual .mdb
b. Word appears to check the version of the Access program it is using when
it connects via DDE, but I do not know how it uses that information.
c. To use secured Access 97 databases in Access 2000 you need Access 2000
to be using the same workgroup security file (AKA security file or system
database) as the Access 97 database requires, or to convert the security
file. I wonder whether you actually have Access 97 set up to use one
workgroup file and Access 2000 set up to use another (or none at all, which
is what I suspect the situation is here).
d. Word does not know anything about which system database to use when it
connects via DDE - it relies completely on Access to do the right thing.
Something you could consider is using ODBC to connect to the data and bypass
Access- in that case you should be able to set up either an ODBC DSN (System
or User) which specifies the appropriate workgroup database, username and
password, or specify all the info. in the connection string of a call to
OpenDataSource in Word VBA.