Prevent access to folder on server by users, but they may change data

[noorani]

we have windows 2000 professional server operating system, as a server, and users have different version of windows.

I have split my Access database b/w FrontEnd and Backend.

BackEnd database is on the server , and all the LAN users having the copy of the FrontEnd installed on there computers, this FrontEnd database having the link to the BackEnd database . now the problem,

i have created a shortcut to users desktop, so they can execute the FrontEnd database which is linked to a Backend database on the server. and every thing works perfectly...

Problem starts, user have the access to the Folder where this BackEnd Databse exist, i mean the folder on the server.

and some time user may delete the whole folder or database without my knowledge.

how can i avoid users to have direct access to the folder where the Backend exist, but at the same time provide them full access to BackEnd database only so they can Add , Edit or Delete records using there FrontEnd Database copy which i installed on there computers.

or in other words user may use the files in the folder but can't delete them. so they can Add, Edit or Delete the data in the database but can not delete the folder or database it self.

how can i solve this problem..

Please advise me.

thanks in advance.

 

[TheGrey]

I see what you want to do.. I'm not very familliar with Access , at least not as a database server, but isn't it possible to set rights in the databases? Or allow the front end database (as a user) to connect to the back end, and just deny the users?

 

[noorani]

The folder on server is a shared folder , and if i make this folder read only then user can not Add or Delete the records on database.. i already have rights set in my database it means that some user can not access some part of my database. and it work pefectly, but i'm afraid of direct access to the shared folder from the client computer.

 

[Seaspray0]

I see two possibilities. One: Hide the folder by putting a $ sign at the end. It makes it a hidden share. Its not perfect but it will keep dummies out (the ones most likely to mess it up). Two: you would have to set the desktop shortcuts to "run as" a different user who had rights to the database. You can give access to the database only to this user. Users would have access through the shortcut because it is "run as" the user you give the access to but not have access directly. The problem with that is, every user will look like the same run as user to the database.