Password Question

  • Thread starter Thread starter Günter Brandstätter
  • Start date Start date
G

Günter Brandstätter

Hi all,

I have an Access frontend-backend database where I implemented some
printouts of documents in MS-WORD. I wanted to secure the Backend-DB with a
password. If I do this, my primtouts don't work anymore. I am using
mailmerge and in the OpenDataSource I wanted to use the Password, but it is
not possible.

objDoc.MailMerge.OpenDataSource Name:=WhereIsDB, ReadOnly:=True,
LinkToSource:=True, Revert:=False, Connection:="QUERY not yet printed",
AddToRecentFiles:=False, PasswordDocument:="Password",
PasswordTemplate:="Password"

How do I implement my DB-password into this OpenDataSource-Command?
Any answer is appreciated
Günter
 
The easiest way is to fake it. Instead of using Access
security, build the security yourself. Doing this may mean
your db security is not quite a robust as what microsoft
has built in, but do you need it that secure? I did
exactly this with one of my database applications. I have
a user table with username and password (and some other
data not important to this discussion). I have a login
form that pops up when the start the application. The user
can not proceed without first logging in. I assign an
initial password that the user is not allowed to use
themselves and require the user to change it when loggin
in on the initial use. The user enters their user name,
then types in their password. If the password does not
match the password stored in the user table, they are not
allowed to proceed.

I decided to do this because I was having a great deal of
trouble with the built in security.

Hope that helps!

Kevin
 
Hi Kevin,
thank you for your response. I know that this kind of security is not quite
the thing. I did the same as you with my other databases, but in this case I
wanted to use the DB password just to prevent the user not to delete or
change anything in the backend accidentially. Now, when I open my WORD
mailmerge document, I need to type this password each time. This is what I
wanted to "automate" by code.

thanks again
Günter


--


-------------------------------------------------------------------------
FIGHT BACK AGAINST SPAM!
Download Spam Inspector, the Award Winning Anti-Spam Filter
http://mail.giantcompany.com


"Kevin" <[email protected]> a écrit dans le message de
The easiest way is to fake it. Instead of using Access
security, build the security yourself. Doing this may mean
your db security is not quite a robust as what microsoft
has built in, but do you need it that secure? I did
exactly this with one of my database applications. I have
a user table with username and password (and some other
data not important to this discussion). I have a login
form that pops up when the start the application. The user
can not proceed without first logging in. I assign an
initial password that the user is not allowed to use
themselves and require the user to change it when loggin
in on the initial use. The user enters their user name,
then types in their password. If the password does not
match the password stored in the user table, they are not
allowed to proceed.

I decided to do this because I was having a great deal of
trouble with the built in security.

Hope that helps!

Kevin
 
What is to stop someone from creating a new database, linking to the tables
in your unsecured database, & reading the usernames/passwords directly out
from your users table?

TC


The easiest way is to fake it. Instead of using Access
security, build the security yourself. Doing this may mean
your db security is not quite a robust as what microsoft
has built in, but do you need it that secure? I did
exactly this with one of my database applications. I have
a user table with username and password (and some other
data not important to this discussion). I have a login
form that pops up when the start the application. The user
can not proceed without first logging in. I assign an
initial password that the user is not allowed to use
themselves and require the user to change it when loggin
in on the initial use. The user enters their user name,
then types in their password. If the password does not
match the password stored in the user table, they are not
allowed to proceed.

I decided to do this because I was having a great deal of
trouble with the built in security.

Hope that helps!

Kevin
 
Good question, but in my databases, where I used username/Password tables, I
scrambled the passwords before writing them to the tables.
This still does not answer my orginal question.
I just wanted to know, if it is not possible to tell WORD to open a
password-protected database without typing the password each time by hand.

thanks again
Günter
 
I think it is not possible to specify the database password when using the
Word OpenDataSource method.

HTH,
TC
 
Back
Top