Re: Securing a Database with Linked tables to different mapped drives

Hi Immanuel :-)

Yes, we do a nightly back-up of the entire Network drive (I've had to
restore the front-end twice because one of my users keeps trying to make
changes to the form and has no idea what he is doing!) So as long as our
Networks group does the nightly back-up I don't feel too uncomfortable
having all the users access the same front-end copy. I do understand that
this is not recommended, but I just don't see a practical solution, short of
me going to each individual users desk and making a copy (which isn't really
feasible)...I just don't trust the users to do this for themselves. I think
I will make a copy of the fe & be and experiment with securing it in a
different Network location where it won't affect anyone. Once I have it
working properly then I can try securing the original database (after making
a good back-up of course!)

Thanks so much for all of your help & advice - I appreciate it!

Coleen

"Immanuel Sibero" <goahead@xxxxxxxxxxx> wrote in message
news:eDPotqmgFHA.1948@xxxxxxxxxxxxxxxxxxxxxxx
> Coleen,
> Comments inline
>
>
> "Coleen" <coleenholley@xxxxxxxxx> wrote in message
> news:%23W6D4QmgFHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi Immanuel :-)
> >
> > The Internet connection is a T-1 line, but our users don't seem to have
> any
> > problems connecting - we just have your normal LAN Network - we are all
> set
> > up to connect to the Server (I think?). I'm not all that versed with
> > Network technology, but I do know that no one is connecting remotely.
We
> > just have users in 3 cities that all connect to the same Network
Servers.
> > I'll just do this one step at a time and hope the users can follow
> > instructions...especially since I will have to send them good
instructions
> > on how to create the desk top Icon to open the database once it's
secured
> > properly (which I know I'll end up spending time on the phone with most
> of
> > them to walk them through it!)
> >
>
> I'm assuming that your users execute the same copy of the front end (FE)
on
> the server which is not recommended.
> I would make sure I have good regular backup of FE and BE. If you start
> seeing dropped connections, improper exit of Access, then this is where I
> would start looking.
>
>
> > When I originally set up this database, I split it (using the method
shown
> > in the link) at that time I only had 3 or 4 users all at the same
location
> > using it and it had not been requested to limit the users to certain
forms
> &
> > reports. Now it is, and since the database is already split, I'm not
sure
> > how to implement the security on the linked tables. Should I just back
it
> > up, import everything back in with the tables, secure it and then
re-split
> > it? That seems like a lot of extra work, but if that's what it takes to
> > secure the database, that's what it takes....
>
>
> I would consult the security FAQ to answer your question. You can secure
an
> unsplit database, or an already split database (by securing both the FE
and
> BE, no need to combine them first). But understanding the security FAQ to
> the letter is the key.
>
>
> Immanuel Sibero


.

Relevant Pages

  • Re: How to secure a split db?
    ... before securing the database. ... Instead, secure it manually. ... >> extra/different steps when converting to MDE? ...
    (microsoft.public.access.security)
  • Re: Securing a Database with Linked tables to different mapped drives
    ... > different Network location where it won't affect anyone. ... > working properly then I can try securing the original database (after ...
    (microsoft.public.access.security)
  • Re: Multiple dbs with shared mdw
    ... > workgroup file which is also on the network. ... > secure other network databases with the same workgroup file. ... Assuming these other network databases are currently not secure, ... join the workgroup file used to secure the one database and then secure the ...
    (microsoft.public.access.security)
  • Re: Securing a Database with Linked tables to different mapped drives
    ... > Networks group does the nightly back-up I don't feel too uncomfortable ... You really really don't want users accessing your database over a WAN. ... > working properly then I can try securing the original database (after ... It's fairly easy to secure the split database. ...
    (microsoft.public.access.security)
  • Re: Workgroup and Security Help
    ... an unsecured database on the common, shared network folder, but maintain the ... original database in my locked, secure personal folder. ...
    (microsoft.public.access.security)