Re: Back end not secured.

"Dylan Moran" <DylanMoran@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D82C40A5-66ED-4ACA-8623-FAF87F2BF9A8@xxxxxxxxxxxxxxxx
> Hi Keith,
>
> Did as you said and still the same. I opened my secure front end, then
> close
> it but keep Access open. Open a new blank database and import all of the
> objects from the unsecured BE. Then opened my front end and linked to my
> new
> backend. But still the same result, no security on directly opening the
> backend. Can you explain how your process applies the security to the new
> backend.
>
Well that was just the starting block. I assumed that, since you'd secured
your FE that you'd know to remove permissions from the "users" group - did
you do that for all objects, including the "database" object?

Regards,
Keith.
www.keithwilby.com


.

Relevant Pages

  • Re: User Accounts
    ... Is it possible to secure both or do i have to leave the backend open?? ... > User-Level security is not easy to implement. ... >> so some of the programming term lose me. ...
    (microsoft.public.access.security)
  • Re: New to security have questions before plunging
    ... > Thanks Keith, ... > this with security? ... It should be rare that you would need to add a table/field to the backend, ... Joan Wild ...
    (microsoft.public.access.security)
  • Re: Back end not secured.
    ... > When you secure a split database, it appears the back end is not secured. ... > That is if you explore to the location of the backend, ... Open your secure front end, then close it but keep Access open. ... HTH - Keith. ...
    (microsoft.public.access.security)
  • Re: splitting a database
    ... > using the same for the BackEnd. ... > - Shortcut to open the FrontEnd Database ... > database using the same secured *.MDW file. ... but it doesn't address the need to secure the backend. ...
    (microsoft.public.access.security)
  • Re: Securing the Back-End
    ... > The workgroup information file that I am using is stored on the ... > database and look at the information in the tables. ... You can secure the backend. ... The key is to use the same workgroup file to secure the backend. ...
    (microsoft.public.access.security)
Quantcast