Network + Linked Tables + Front End + Access Security

  • Thread starter Thread starter Vince
  • Start date Start date
V

Vince

Hi,

Ingredients:

Novel Network
Windows NT OS
Corporate.mdw (Security Key)
CCorp.mdb (FRONT END)
CCorpTables.mdb (Tables)


I am having trouble securing the linked table database...

How can I do it allowing users to properly use it without
seeing the data but able to write to the tables and not
allowing them to delete the entire database?

I tried to not allow opening of DB but it won't work,
users can't open data....what do I set for novell rights?
Read and write only?

I was told to set the folder with the security key with
full rights, I don't care about the key cause I can
always restore it globally if users delete it for any
strange reason....

HELP!!!

Thanks!

Vince.
 
I am having trouble securing the linked table database...

How can I do it allowing users to properly use it without
seeing the data but able to write to the tables

For the above, you don't need to use any secirty seetings. In any well
develpoed access apcptlion the talbes view, the desins view etc is hidden
from the user. This is NOT a seicrty issue, but simply one of provind a nice
user interface. Generally this sotlion is done by distrvuiton a mde to each
users workstation (by the way, the correct way of deplayoing an access
appcton on a network is to give EACH USER THEIR OWN copy of the mde (the
front end). This front end as a mde thus cannot be modifed (code, forms
etc.). This front end goes on each pc. If you are not placing a front end on
each pc, then your setup is poor.

Of couse, using the tools->startup options in sma-ccess you can compility
hide and withhold the ms-access interrfae (such as lookiing dirclity at the
tables etc). You don't need code, and you don't need ms-access secirty to
accomplish this at all. You can download a sample mdb setup this way. Check
out:

http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.htm

Download the 3rd small example in the above. The above 3rd example is NOT a
mde, and the shiftkey has not been disabled. So, to view the settings I
used, you can exit the little appcltion and then re-load the appltion, but
hold down the shift key. You can then look at the settings useing in the
tools->startup to hide the ms-access inteface. Of couse, to further keep
users out of hte ms-access intefce, the shift key option would be dis-abled.

Doing all of the above takes no code, nor does it take any secirty settngs
or even a work group file.
and not
allowing them to delete the entire database?

Well, remember, we are using ms-office here. You can't stop usrs from
deleteing a Excel document. You can't stop suers from delering a word
docuemnt. You can't stop users from delering a ms-access documnt. (a file is
a file is a file......a horse is a horsue is a horse).

Futher, for the appction to furcntion correclity, your usres need FULL
RIGHTS to that dir. That means create, delete, read, write...the WHOLE BALL
of wax.

So, not sure if your question is about keeping people out of looking at the
tables and the database designs directly (that can be done without any code,
and without using security).

However, if you are talking about preventing users from deleting the file
from the shared dir, you can't do that. However, if you have been providing
a nice front end mde installed on each pc with the ms-access interface
hidden, it would be very unlikely that users even know, or care where the
back end file is.

If you need a secure system where users MUST not be able delete the back end
file (this is a different issue then going into the tables...which you can
easily prevent), then you can't use ms-access. You can use the other
database engine that is on the office CD (the sql desktop edition has been
included on the office CD for the last 3 versions). When Using this free sql
server engine you can complete hide and complete prevent your users from
touching or browsing to, or even deleting those datafiles. This sql server
engine of course requires windows to run, and thus will not work on Novell.

If you need a high security system where it is not possible for users to
copy the document, then word, Excel, or a shared mdb file is not going to do
the trick here.
 
Thanks for the info...but users can still go and open the
source db where all the tables are stored...my problem is
still there?

Will hiding it really work? How...?

Thnks
Vince
 
SQL Server runs as a "service" ... users don't require access to the actual
data files to be able to use the data contained there. Also, you cannot
delete or move the data files while they're attached to the server (you can
stop the server and delete them, but that requires a login with Admin rights
on the server). Properly secured, with proper use of Views, Stored Procs,
and other SQL Server tidbits, it's as secure as you can get ... and you can
further encrypt pretty much any portion of the various SQL Server objects
....

Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP

"Smash forehead on keyboard to continue ... "
 
Vince said:
Thanks for the info...but users can still go and open the
source db where all the tables are stored...my problem is
still there?

There are a couple of things you can do to stop them, however if they are
determined they can still get at the file.

1. put the backend in a hidden share \\server\share$ rather than
\\server\share
2. put an autoexec macro in the backend that closes the file after throwing
up a message telling them to open the frontend to access the data.
3. disable the shiftkeybypass in the backend.

Again, the determined can get by these things.
 
Hi Joan,

I think Vince was talking about Albert's suggestion to use SQL Server or
MSDE, and he was asking if users could simply go to the SQL Server datafiles
and copy them ... unless I misunderstood his post (which wouldn't be the
first time!!)

Scott
 
Back
Top