BE in secured file on server

  • Thread starter Thread starter CarlaInJax
  • Start date Start date
C

CarlaInJax

I have a split database with the BE on the server. Someone went into my file
on the server and deleted over 2,000 records from my table. In an effort to
keep this from happening again, my IT people set it up so that only I could
access my file on the server. Now when users click on the FE that is loaded
on their machine, they are denied access to my file. Is there a way around
this so that users can access the data they need, but leaving the BE in my
secured file?
Thanks.
 
CarlaInJax said:
I have a split database with the BE on the server. Someone went into
my file on the server and deleted over 2,000 records from my table.
In an effort to keep this from happening again, my IT people set it
up so that only I could access my file on the server. Now when users
click on the FE that is loaded on their machine, they are denied
access to my file. Is there a way around this so that users can
access the data they need, but leaving the BE in my secured file?
Thanks.
Click to expand...

Not really, That is the nature of a file-based database.

You can implement Access User Level Security to limit what people can do
based on permissions, groups, etc, but that is an advanced topic, and even
that can be defeated by someone determined enough to obtain the utilities to
do so.

For better control than that you would need to use a server back end like
SQL Server.
 
OK, so rather than have my IT guys unsecure my file (I have other stuff I'd
like to keep secure), I copied my BE to the served in an unsecured file and
and linked my FE to the new BE. However, it is now telling me that the
command could not be executed.
?Any ideas?
 
am a little confused;

..mdb User Level Security can prevent a normal user from accessing the
backend directly.

It can also (along with the front end design by you) prevent them from
deleting records via the FrontEnd. Don't over look this; depending on your
design they may have deleted the records without even directly goint to the
backend file....

It is true that a confirmed cracker can pretty easily find ways around this
- - but most casual work related malicious/accidental will be stopped....
 
Back
Top