By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,027 Members | 1,273 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,027 IT Pros & Developers. It's quick & easy.

Password for backend

P: n/a
I have developed a program that has the backend on a server and
multiple users have the front end at their individual computers.

I know how to set a password on the backend. How can I implement the
requirement for entry of this password for each user as they sign in on
the front end?

Thank you for the help in advance


Nov 13 '05 #1
Share this Question
Share on Google+
6 Replies

P: n/a
Hi Mike,

the answer to the question depends on what you are using on the backend
to store the data.

1. MS-access, then using the access based security with the program
"workgroup administrator' wrkadmin.exe is the best way to setup a login
system, access using a system where by default everyone is logged in
using a user of Admin, when setting a password for this account then
everyone is asked for a username and password. This system is not
strong security, and if all you are trying to do is identify them e.g.
who wrote this record etc, then you can use the WinAPI to get the
currently logged in username.

2. SQL you can setup logins on the SQL server so that server based
security is used, this is far stronger than access based security.

If you need more details on access security just post here.

Hope it helps


Nov 13 '05 #2

P: n/a
"Alex - IntraLAN" <al**> wrote in message news:<11**********************@f14g2000cwb.googleg>...
Hi Mike,

the answer to the question depends on what you are using on the backend
to store the data.

None Alex.

I just want to stop the user from editing the tables by opening the
BackEnd.mdb, which is a ms access 2000 db.

The only way to use the tables is by opening the FrontEnd.mdb.

I only need to set a password for the database itself (BackEnd.mdb)
and open it
only from the mainform in the FrontEnd.mdb

I use DAO and have tried ADO examples as well (given in the developer
edition and the KB-articles on, but nothing seems
to work. So I wonder...

I use win 2000 on one disk and win 98 on another. Both refuses to
accept the simple password : "1234567890aha" as a test.

They claim: "Invalid password".

Now I've opened the BackEnd.mdb in exclusive mode and I've set the
password as written.

I've checked that DAO reference is the first (doesn't use ADO so far)
in the reference box.


I can report, though, that the sun has returned in Northern Norway,
and it feels good!

Nov 13 '05 #3

P: n/a
Hi Geir,

Are you linking your back-end and front-end with the linked table
options in the front end, because if so then you should only be asked
for the database password when doing the linking process from that
point onward the front-end will store the database password in itself
so that you won't be asked to enter it again. The following is an MS
doc for opening via automation, but is sounds like we have gone further
than that. If you have linked all the table from the back-end into the
front end you should not have to worry about the password as your code
with reference the tables as if they are local to the database. Try an
easy password like 'day' just for testing.
Hope that helps a bit



Nov 13 '05 #4

P: n/a

I'll try your suggestion and see how it work.

Thanks for answering!

Nov 13 '05 #5

P: n/a
Hi Alex!

It works!

However, I had to put the calling of the code in the pop-up form,
displays for 1250 ms, in order to avoid access 2000 load a new
database window each time I opened, say...frmCustomer or another form.

Now it works very well.

Thanks again!

Nov 13 '05 #6

P: n/a

I have solved the problem of backend password.

1. Go to backend - open it exclusively and give it a password.

2. I use .connect and link to each table in the backend. Within this
connect link, you can provide the password at the time the link is made
using ";PWD = Yourpassword". You can then use the tables in the backend,
even though they are password protected.

3.You can also open front end exclusively and give it a different
password if you wish to protect front end.

*** Sent via Developersdex ***
Nov 13 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.