Re: Front end, Back end, and restrictions on which Forms can open.

Tech-Archive recommends: Fix windows errors by optimizing your registry



It isn't working.

I do the Ctrl+O after securing the front end and secure teh back end
using the same method and selecting the same security file. It says it
is secured but when I double click on the file, it still opens without
asking for user name and psw. what am I missing?

And do I need to secure the FE at all if it is an MDE file?

Joan Wild wrote:
mpfohl@xxxxxxxxxxx wrote:

1) I've used the security wizard but that only secures the front end.
Do i just run the same wizard to secure the back end?

No. I would open the frontend using the desktop shortcut the wizard created
for you - this'll ensure you are using the same workgroup as you used to
secure the FE. Now hit Ctrl-O and open the backend. Now you can run the
wizard - choose to modify the existing workgroup file, rather than creating
a new one. This will secure the BE and it will also create a desktop
shortcut to the backend - delete this shortcut. Now open the FE again and
refresh the links to the new secure backend mdb.

2) I have one form that I would like to restrict access to (it is for
administrative functions on the database). Is there a way to set
permissions to that specific form so that the Administrator can open
it but the average user cannot?

I assume you have some Group that 'Administrators' belong to. Grant open
permission on this form to this group and deny permission to all other
groups. If this form has a recordsource, then the Administrators will also
need at minimum Read Data permission on this table/query.

--
Joan Wild
Microsoft Access MVP

.



Relevant Pages

  • Re: IIS on DMZ
    ... I understand what you mean but security team basically is saying IIS is not ... also on DMZ but firewall opens up only port 80/443 on the proxies. ... But there is no such thing as "perfectly secure". ...
    (microsoft.public.inetserver.iis.security)
  • Re: multiple mdws
    ... > Yes, secure your database. ... > just goingin to Security and adding some groups and changing their access. ... search for a database and the full version opens the secured ...
    (microsoft.public.access.security)
  • RE: security wizard cannot be run
    ... secure mdb while joined to system.mdw. ... database is very secure) ... Open Access (no mdb). ... Once the database opens, the ...
    (microsoft.public.access.security)
  • Re: User Accounts
    ... You just need to join the same workgroup that you used to secure the ... > Ok i have been able to secure the front end .mdb (I was using an mde ... >> User-Level security is not easy to implement. ... >>> What i want to do is when a user opens the mde there is a pop up ...
    (microsoft.public.access.security)
  • Re: multiple mdws
    ... Yes, secure your database. ... just goingin to Security and adding some groups and changing their access. ... search for a database and the full version opens the secured ...
    (microsoft.public.access.security)