Securing the back-end .......

  • Thread starter Thread starter m.cringle
  • Start date Start date
M

m.cringle

Hi guys

I'm really banging my head against a brick wall with this one - Please
help!!

I have split my database and managed to secure the front-end exactly
how is needed. However, I'm really having troubles securing the
back-end with the same workgroup. I have managed to lock myself out a
number of times but fortunately I have gained access again.

Can anybody tell me exactly how to do this? My book doesn't go into any

detail about how to actually do it!


Really appreciate it :-)
 
Open the back end while in the secure workgroup and set the permissions on
the tables. Generally, you can secure the back-end with the server alone,
The server will not allow anyone without permissions in the group to connect
to the tables. The only time I ever secure the back-end is if I need to let
some people have read-only access. Then I set up a read-only group in
Access.

Another method of securing the back-end is to taje away all permissions from
everyone except the database owner and then write every query to give users
WITH OWNERACCESS OPTION.

Read the Security FAQ very carefully and you'll get the answers to your
specific questions:

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Sorry Arvin, Not safe enough.
Create a new database using the secured .mdw & import the tables &
relationships from you back-end
Then set the Groups & User security on the tables in the new BE, remember to
remove Access from the Users group in particular.
For the rest read up on the Security FAQ for the sordid details <g>
Pieter
 
I'm very confused. I tried this but I can still open and edit the back
end with no password.

I have completely removed all permissions from the user group and made
sure that the Admin user is only part of the User group. However, when
I open the database, there is no protection and I'm logged in as Admin
user.

How can this be possible?? Admin shouldn't even be able to open the
database!

p.s - when i imported my tables, I clicked the (and relationships) box
but they do not show - is this normal?
I have tried selecting 'show relationships' but no luck

Thanks
 
You should not let the admin user own the database OR be a member of the
Admins Group in your secured Db.
This user is *the same* wether the workgroup is default or not!

Pieter
 
.....but, you Must give the Admin account a password in the secured
workgroup, to avoid beeing silently logged in as that user
or use the /UID=MyDbOwner /PWD=MySecretPWD switches in a shortcut to open
the database

Pieter
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top