MDB with Password Enough?

[infinitx]

Hi,

I have an mdb database that is protected through a password. I have another mdb database (which is the one that the user opens) that opens the first protected database. So the user cannot access the 1st database without a password. I am wondering if this is enough protection or do I have to make the first database a .mde.

The reason why I am asking is that I have been having problems on the users' computers with the mde but no with the mdb.

Do you think that the 1st method is sufficient?


Thanks

 

[Shane_1]

I just got done reading a whole 17 page article on access security. Those simple passwords are really easy for someone with the proper tools to break into.

I would suggest reading into some user-level security....

 

[snakeyes2002]

i take it that you have designed a front-end, back-end system?

Your first database (back-end) contains all the data? and is protected with a password? and is on a network drive away from prying eyes?

your front end (user database) looks at backend data using password? returns data requested,data user allowed to? contains most of the code - (your code)? saved as an mde?

as long as you make a backup of your front-end mdb before you create an mde then I do not see a problem with your security - unless some1 was to deliberately inflict some damage - (delete the backend?!!)

maybe ask your IT guys to protect a file within a folder from being deleted - or maybe you are allowed to do that yourself?

i think like that all the time - is somebody out to get me.... probably...

 

[snakeyes2002]

on another note - do you trust the users of your database?
or everyone that has access to it?

 

[infinitx]

I have a front-end database protected with a password. I also have a back-end database to it which is not protected by a password.

Then I have another regular database (not split into FE & BE) which just launches the first front-end database and enters the password for the user.

So the user can still run the 1st front-end database without having the ability to actually open it and see what is inside without knowing the password.

Also, this is not on a network, it is just a reuglar distributable program.

Is that more clear?


Currently, I have trusted users by later, that might not be true.

 

[snakeyes2002]

oops, i went a wee bit mad there - off on a tangent. were security is concerned - password security should be fine - i dont use any (any of the users using my system wouldn't have a clue how to delete a record, never mind a line of code)

but, that's just my opinion. i'll look into some other options for you and get back next night - maybe some1 else has a bit better of an idea

 

[ghudson]

There are too many freeware programs available on the internet that will crack the user "open database" Access password. I have yet to see or find a "free" program that will crack Access workgroup and user permission security. An unsercured database can be easily linked to. The unsecured data can be read, deleted and/or altered. The design and VBA of an unsecured db can be read, deleted and/or altered. Just about anything can be hacked but you at least make it more difficult with the more effort you put into your db security.