Front End / Back End & Password Protection

  • Thread starter Thread starter Duncs
  • Start date Start date
D

Duncs

I have a back end / front end database, with the front end converted
to an .MDE file. What I would like to do is put a password on the
back end, so that no-one can "accidentally" stumble on the data, and
modify it. I tried setting a password on the back-end, but when I
open the front-end and try to access a linked table, it gives me an
error message saying:"Not a valid password."

Also, when I try to open a form that links to one of the tables in the
back-end, this also gives me the same error.

How can I achieve this?

Rgds

Duncs
 
Did you try
== assigning the password to the backend
== dropping all the links in the front end
== relinking to the tables in the backend and saving the password when prompted?

Of course, you would want to do all this on a copy to test it.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
 
I have a back end / front end database, with the front end converted
to an .MDE file.  What I would like to do is put a password on the
back end, so that no-one can "accidentally" stumble on the data, and
modify it.  I tried setting a password on the back-end, but when I
open the front-end and try to access a linked table, it gives me an
error message saying:"Not a valid password."

Also, when I try to open a form that links to one of the tables in the
back-end, this also gives me the same error.

How can I achieve this?

Rgds

Duncs
Click to expand...

Did you set up the password after you linked the tables? If so, you'll
need to re-establish the link and provide the password to the front
end.

Keven Denen
 
On Mon, 19 Oct 2009 04:33:36 -0700 (PDT), Duncs

The password can be embedded in the linked table when you refresh the
links.
But I would simply put an AutoExec macro in the BE, which runs a
MsgBox statement: Yo, you're not supposed to be here! This is the BE
for the XYZ FE. It will close now.
DoCmd.Quit.

-Tom.
Microsoft Access MVP
 
Duncs said:
I have a back end / front end database, with the front end converted
to an .MDE file. What I would like to do is put a password on the
back end, so that no-one can "accidentally" stumble on the data, and
modify it.
Click to expand...

I have a startup form which basically tells the user they can't do
anything there. Various special keys are inhibited although not all
of them so I can still get into it to make schema changes.

On that startup form I also display the full name and path of the MDB
as well as the number of records in one or two key tables. This way
if they are trying to restore something from backup or moving files
between computers they can easily figure out what's what.

Hmmm, I should add the last transaction date as well.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
 
m:
What I would like to do is put a password on the
back end, so that no-one can "accidentally" stumble on the data,
and modify it.
Click to expand...

Database passwords are completely worthless for an purpose
whatsoever.

Several things to obfuscate your back end:

1. name the share on the server with a trailing $, as in Database$.
It will remain accessible when requested explicitly by name, but
will not show up when browsing in Windows Explorer (either Network
Places or in the File Open dialogs).

2. hide the database window and turn off the AllowByPassKey option.
Search VBE help for "AllowBypassKey". You'll find code to do the
job.

3. implement user-level security so the users can't get to the data
without the appropriate user logon. If you lock down the back end
and use RWOP queries in your front end for loading data from the
back end, your users won't be able to even *view* the data in the
back end without cracking ULS (and that's not that hard).

4. if you really actually need to protect the data, you are using
the wrong data store, as the only thing you can really do with a
Jet/ACE back end is security by obfuscation plus Jet user-level
security (which is crackable for those who have bad intentions).
 
Back
Top