Back end security

  • Thread starter Thread starter A Hopper
  • Start date Start date
A

A Hopper

I have a database front end MDE, back end MDB. The back
end resides on Drive L of a network. All workstations use
Access runtime and updates are sent out using Update by
Tony Toews. Drive L is visibls and accessable to all
workstations, which means that by going to My Computer
opening Drive L anyone could delete the back end of the
database.

Is there a way to make Drive L secure and still have the
front end be able to connect to it?

I am looking into adding security to the database, but am
very nervous about doing it. It seems complicated when I
thing about permissions - tables, fields, forms and what
users are allowed to do design, data entry, edit, read
only. Presently I keep forms invisible to limit access but
this is not adequate so security has become a necessity.

I appreciate any help to impliment security.

Thanks
Allan
 
A Hopper said:
I have a database front end MDE, back end MDB. The back
end resides on Drive L of a network. All workstations use
Access runtime and updates are sent out using Update by
Tony Toews. Drive L is visibls and accessable to all
workstations, which means that by going to My Computer
opening Drive L anyone could delete the back end of the
database.

Is there a way to make Drive L secure and still have the
front end be able to connect to it?
Click to expand...

Not that I know of. You could create your links with a UNC path instead of
a mapped drive.

\\ServerName\ShareName

Then the server folder could be shared, but hidden and you would not map a
drive to it. This would make it somewhat difficult for most of your users
to even figure out where the backend file is located.
 
As Rick said, you can use a hidden UNC instead of a mapped drive. This is
about the best you can do. For sharing a Jet database, Jet has to be able to
fully manage the ldb file, so the server share must have *full* rights,
including create, modify, and delete. Because of that, the file itself is
anything but secure.

Unless you have "hacker" users that like to be malicious, the hidden folder
should get the job done.

However, if they are familiar with Access, you'll also need to lock the
front ends. An mde is not enough. A slightly Access savvy person can easily
figure out the table links and can get the UNC.

If it's data that must be truly protected, no file-share database, including
Access, is going to work. You need to go to a client/server database engine
like SQL Server, Oracle, DB2, etc, on the server.

Good luck.

Sco

M.L. "Sco" Scofield, Microsoft Access MVP, MCSD, MCP, MSS, A+
Useful Metric Conversion #17 of 19: 1 billion billion picolos = 1 gigolo
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
Back
Top