Split database security

[jaitken0308]

Hi,

I have a database that I just split into a front/back end, and have a question about protecting the back end data.

I know that the back end must be in a place the front end user can access, but do they have to actually be able to open and access the back end for the links from the front end to work?

Here's why I'm asking:

My front end has a user table and a login form with a DLOOKUP function to verify their credentials. And the front end is so locked down for the user (no navigation pane, no ribbon, no shortcut keys, no shortcut menus - only the ability to log in and out and use the main menu form) that they couldn't do much damage if they tried (minus jacking up some records).

My back end has nothing yet but the tables. If I use the Access "Encrypt Database" feature to give it a password, then it seems to affect the front end and tells me I haven't entered a valid login, even though my front end is not encrypted in this way. If I do to my back end what I did to my front end (user table and login form), but only allow one user (me), will they be able to edit data in the front end and have it translate to the back end if they can't actually access the back end by opening it?

I don't want them in the back end at all, and I don't want to chance them stumbling upon it and inadvertently damaging data. Any suggestions?

 

[Galaxiom]

Access back ends are never really fully secure. If you want real security you need to use a database server backend such as MySQL or MS SQL Server.

 

[jaitken0308]

Access back ends are never really fully secure. If you want real security you need to use a database server backend such as MySQL or MS SQL Server.

Unfortunately, that isn't an option here. I could always just hide the back end - somewhere where they can access it of course.

But I'm still wondering, if I create a login requirement on the back end and only allow me, will they be able to update the front end and have it transfer to the back end if they can't actually get into the back end?

 

[Galaxiom]

You can password protect the backend. However the password would be stored in the front end and can be seen in the Connect property. It is possible to build the Connect property from an encrypted password stored in VBA. However since the backend is a file which users must be able to access there is no way to stop them taking that file offsite and brute forcing the password. BTW. MS SQL Server has a free edition. It is reasonably easy to convert the back end to it. You get the data limit increased to 10GB too. Access stops at 2GB.