backend table protection

[Lifeseeker]

Hi,

Is there any way to physically protect the backend?

One way of doing it would be to create backups every day, but this still won't prevent ppl from accessing the folder and deleting the backend.


Any thought on this guys?

thank you

 

[Beetle]

Unfortunately, with an Access (.mdb or .accdb) back end, there's not a whole lot you can do that can't be easily worked around by someone with even a mild amount of knowledge about computers. This kind of falls under the category of ignorance is the first line of defense. The vast majority of users probably would not have the know how, or the desire, to sniff out the back end on the network and delete it. Of course it could always happen accidentally, or if you work in an environment where your user base is generally knowledgable about computers and you've got someone who is intent on causing havoc, they'll be able to do so. Your best option if you are really concerned about something like this happening would be do use a more secure database like SQL Server (the Express edition is free) for the back end.

 

[Galaxiom]

Where I work we use a Group Policy to prevent users from browsing UNC network paths and map any shares they are allowed to have. All sharenames end with the $ to stop them being listed in the network neighbourhood.

Access backends are located on UNC shares so user don't ever come across them.

Most users only have Access Runtime and all the databases are started with the runtime switch so even users with the full version get a runtime experience. Consequently they don't see the tables or the path on the table links.

It wouldn't keep out the determined user but ordinary users don't find them.