Merge with secured Access db

[Russ]

I have a W2k doc that is a catalog page type of mail merge
document. I use it to select a single record from teh
database with many merge fields and create nicely
formatted page representing that record. I developed it
using an unsecured Access 2000 db which works perfectly.
I have recently secured the database and even when I log
into the db as administrator with full privileges I get an
error message that I do not have read permission on the
query that is the datasource. I know that the datasurce
was changed since I am asked for the password when the
document opens. I am using Word rather than an Access
report since the document has a lot of detailed formatting
requirements. Any ideas?

Thanks!

 

[Peter Jamieson]

How are you connecting to the datasource from Word?

And how did you create the query that you are using as the data source?

 

[Russ]

Thanks for the reply. The query was created within
Access. I am using DDE method of connection to Access.

 

[Peter Jamieson]

OK, I think I misinterpreted something you said before. Here's my best bet.
When you secured your Access database, did you decide to
a. make the new workgroup file the default workgroup file (i.e. for Access)
or
b. create a shortcut to open the secured Access database.

If (b), what happens is that whenever you click on the link, a command line
is issued specifying that the new workgroup file will be used with the
database. If, however, you try to open the database any other way (and that
would include "from Word mailmerge documents", /at best/ the program will
try to open the database using the /default/ workgroup file, which is not
the correct one. So the security checks will always fail. At least, I think
that is what happens.

If this doesn't quare with what is happening where you are, I have guessed
wrongly and we'll have to consider other options.

But if I am right, I think you either have to do (a) instead, or use ODBC to
connect to your database, in which case you should be able to specify the
name of the workgroup file (or "system database" as it is known in ODBC
jargon). And you should be able to make that association by using the ODBC
administrator either to
a. change the properites of the existing Access DSN so that the correct
system database is specified (not a good idea if you need to use multiple
databases with different workgroup information files) or
b. set up a new ODBC DSN specifically to connect to this database.

Either way, if you are setting this database up for use from multiple
machines (either by distributing the complete application, or by setting up
a multi-user database), you will need to ensure that the correct DSN is
available on /all/ the machines that need to connect to his data source. And
that's another story.