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

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




>
> Thanks so much for all of your help with this!
>
> Coleen
>
> "Immanuel Sibero" <goahead@xxxxxxxxxxx> wrote in message
> news:e7nZRklgFHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
> > Coleen,
> > Comments inline
> >
> >
> > "Coleen" <coleenholley@xxxxxxxxx> wrote in message
> > news:OMUnBXlgFHA.1044@xxxxxxxxxxxxxxxxxxxxxxx
> > > Thanks Immanuel
> > >
> > > I do have it set up with a front-end/back-end, but I'm not quite sure
> what
> > > you mean about each user having a copy of the front-end on their
> > > desktop...they all have Access 2000 on their desktops, but they don't
> have
> > > individual copies of the front-end. They are all in different
locations
> > > (cities), so it is impractical for me to go and put a copy of the
> > front-end
> > > icon on each of their desk tops, they just link to it on the Network.
> >
> >
> > I didnt realize that you have remote users. The "one copy of front end
on
> > each user's local machine" approach is good for users on a LAN with at
> least
> > 10 mb/s throughput (the old ethernet bandwith standard).
> >
> > For remote users, it's a different story. A lot depends on the bandwith
> with
> > which your remote users are connected to your network. Even a T1
> connection
> > is too slow for running Access. The recommended setup for remote users
are
> > some type of terminal server or remote desktop configuration where the
> > remote users do not actually load (i.e. execute) the front end on their
> > local machine.
> >
> > How fast are your remote users' connection? From your description, are
> they
> > running Access straight from the server?
> >
> >
> > > We
> > > have a separate Networks Administration group (of which I'm not a
part)
> > and
> > > database/programmers group (of which I am a part) - I have a call into
> our
> > > Networks group to see what it will take to set up a UNC icon for each
> > user,
> > > but again since there are about 20 different users spread across 3
> > different
> > > cities, it makes it difficult to get to each user's desk to set them
up.
> > To
> > > be honest, if I thought they would understand how to set it up
> themselves
> > > I'd go that route...unfortunately some of the users would not have a
> clue
> > > what to do, even with step-by-step instructions! If I have them copy
> the
> > > front-end application from the network to their desktops instead of
> > > double-clicking the Icon that opens the Network version of the
> front-end,
> > I
> > > guess that would work, but again, I'm not sure how many would be able
to
> > > follow that simple procedure! Then I still have the process of
securing
> > the
> > > database with linked tables, even after I solve the Network
problems...I
> > > checked the steps for Access Security from Joan's site and this works
> > > perfectly for a database that doesn't have linked tables (I have one
set
> > up
> > > that way and it works perfectly!), but I'm still at a loss as to how
to
> > > secure this database with the linked tables?
> >
> > Did you check out
> >
> > http://www.jmwild.com/SplitSecure.htm
> >
> >
> > Immanuel Sibero
> >
> >
> >
> >
> > >
> > > "Immanuel Sibero" <goahead@xxxxxxxxxxx> wrote in message
> > > news:uRf4sfkgFHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
> > > >
> > > > Coleen,
> > > >
> > > > If you link to a mapped drive for one user and other users with
> > different
> > > > mapped drives also use the same file (mdb), then yes, it will mess
up
> > the
> > > > other users.
> > > >
> > > > Following are things you can do to address the issue.
> > > >
> > > > - You should link your tables using UNC instead of mapped drives.
You
> > can
> > > do
> > > > this in explorer through Network Neighborhood. UNC will be the same
> for
> > > all
> > > > users.
> > > > - You should also look into how to properly split your application
> into
> > > > Front End and Back End. Each user should have his/her own Front End.
> > Each
> > > > user should run his/her own copy of the application.
> > > >
> > > > HTH,
> > > > Immanuel Sibero
> > > >
> > > >
> > > >
> > > > "Coleen" <coleenholley@xxxxxxxxx> wrote in message
> > > > news:%23RmZiUkgFHA.1948@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > Hi All :-)
> > > > >
> > > > > I have a question about securing a database that has linked
tables,
> > and
> > > is
> > > > > used by multiple users that are mapped to different drives. When
I
> > try
> > > to
> > > > > log into the database, since I am mapped to a different drive I
get
> > the
> > > > > message "path-name.... is not a valid path. Make sure that the
path
> > > name
> > > > is
> > > > > spelled correctly and that you are connected to the server on
which
> > the
> > > > file
> > > > > resides." If I do a Linked Table Manager update, won't that screw
> up
> > > the
> > > > > linked tables for the other users? It's been a while since I've
> > worked
> > > on
> > > > > this, but I seem to remember when I tried this before it messed up
> > > > everyone
> > > > > else's link. I am using Access 2000, any suggestions? TIA,
> > > > >
> > > > > Coleen
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>


.

Relevant Pages

  • Re: Securing a Database with Linked tables to different mapped drives
    ... > individual copies of the front-end. ... > icon on each of their desk tops, they just link to it on the Network. ... I didnt realize that you have remote users. ... > database with linked tables, even after I solve the Network problems...I ...
    (microsoft.public.access.security)
  • Re: Record-Locking
    ... It means that as soon as the front end opens, a connection is made to the ... database locking mechanisms to safeguard the data. ... Bury the back end file deep in the directory structure on a network ...
    (microsoft.public.access.security)
  • Re: is changing design master safe?
    ... Replication is certainly one way, but you are hampered if you don't ... You *can* establish a temporary network ... connection via modem connection and RAS, however, I don't have any ... third database that you *do* copy from location to location. ...
    (microsoft.public.access.replication)
  • Re: Previously opened database connection/path invalid - ADO.NET/OLE D
    ... This sound more like a network connectivity issue. ... network connection is dropping off intermintently so it might be worth your ... > Microsoft Access database using the OLE DB objects (database connection ... > are using Celeron processors and I did have a problem with a Celeron ...
    (microsoft.public.data.ado)
  • Re: Securing a Database with Linked tables to different mapped drives
    ... The Internet connection is a T-1 line, but our users don't seem to have any ... Network technology, but I do know that no one is connecting remotely. ... When I originally set up this database, I split it (using the method shown ... > I didnt realize that you have remote users. ...
    (microsoft.public.access.security)