I would like to password protect ONLY the back end part of linked databases
so my users cannot delete any of the tables contained in the back end. The
front end can remain unsecure. After password protecting the back end only,
it prompted me for the password when i executed the front end. Any
advise...Thanks

Are we talking "database password" or "user-level security"?  The former I
wouldn't know about but if the latter then I would try securing your FE
using the same workgroup as the BE, but allow the "users" group permission
as appropriate *except* the tables.  You could then use RWOP queries to
manipulate the data.  I haven't tried this method per se but it should be a
step in the right direction.  Make sure you back up your files before you
start!

HTH - Keith.

The front end has linked tables.  When each link was created, information
about the table (path, file name, password, table structure, and statistics)
was saved in this link.  If the table or connection information is later
changed in any way, such as new fields added, or a field data type is
changed, or a password is assigned to the database, then the link information
in the front end doesn't get updated.  Now that you have a password on the
database where the table links to, the front end tries to open the link to
the back end with the previous connection information, which didn't include a
password.

You'll need to delete the links, then recreate the links (don't just
"refresh" the links, because that doesn't update the new information you need
for making a connection to the table) to the password-protected database. 
Also, you may have VBA code or object properties that connect to this
database on start up, so search for the name of the back end database in the
VBA code and, if you can't find it there, in the form, query, and report
properties.

If you're worried about the users deleting what they shouldn't, then a
database password on the back end probably isn't enough protection. 
Implementing User-Level Security or linking to tables located in a
client/server database would offer more protection.  At the least, you should
hide those tables, even if all you have is the database password
(Shared-Level Security) for protection.  For some ideas on ways to hide these
tables, please see the following Web page in the Security section for a link
to the tip, "How to be sneakier than the snoops peeking at data they
shouldn’t see":

http://www.Access.QBuilt.com/html/how-to_tips.html

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers.  Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.


Show quoteHide quote

User Tracking in Access
Credit Card Masking
Security without signon
Creating Object and Setting Permissions for it Through Code--Is it possible?
update / kb 904018
Permission problem
Multi-user database with common front-end
security with system.mdw
Password protection
Is it possible...