Question How to lock Access DB

[Sombrero]

Hello...

I'm newbie & don't have much experience in access DB...

I hope I get some advice about how to lock access DB Tables ,Queries, Report so other's can not import them to other access database (without encrypting my database with password).

I've noticed when forms have VBA codes it cant be imported if they locked by password(VBA) !

I hope its clear and sorry for my bad English...

 

[RainLover]

To answer this question it would take a lot of time.

Could you give details about what you have done so far. How your Database is designed. Is it split. Number of users. The version you are using.

Can you post any links you have read and not understood certain parts.

Also what is you prime reason or concern for wanting to do this. Do you want all parts secured. Are we looking at different levels for different people.

This may be enough to get us started.

 

[Sombrero]

To answer this question it would take a lot of time.

Could you give details about what you have done so far. How your Database is designed. Is it split. Number of users. The version you are using.

Can you post any links you have read and not understood certain parts.

Also what is you prime reason or concern for wanting to do this. Do you want all parts secured. Are we looking at different levels for different people.

This may be enough to get us started.

Thanks RainLover for reply & response...

Details:
DB is designed by access 2010 (not encrypted by password) , I've managed to add login form as front end for user and hide other unnecessary tool such as navigation pane, menu bar, ribbon bar, etc....

DB is located on domain network to be used by multi user (that's way I don't want to be encrypted by password)...

my concern: I don't want anyone able to see tables, Queries (data & structure) by any means...

I've test my DB to be publish as an ACCDE format but importing issue a still appear for tables and Queries...

I'm not sure about splitting data case will solve the issue because as far as I know it for performance over a network ...

I hope this clarify my issue...

Any ideas PLZ..

Regards...

 

[RainLover]

I'm not sure about splitting data case will solve the issue because as far as I know it for performance over a network ...

This is the first thing you should do. Each user should have their own front end on their own machine and linking to the Back End which should reside on the server.

I would also password protect the back end.

The next would be to disable the by pass key.

You may need to Google each topic for help as you go.

There will be a limit to the amount of help I can give as I am not familiar with 2010.

 

[Sombrero]

Thanks "RainLover" for your time and efforts to help...

Disabling by pass key it's already included in my DB project as part of security concerns...

Splitting Database is the area which I have to dig it likely more...

currently all my testing carried out on virtual environments to check and reduce any weakness regarding DB security before real world production...

Would you recommend to use old .mdb format due it has "Group & User Permissions" feature?

Anyway I will do more research on your suggestion topics...

hopefully I can see the "big picture"...

Regards...

 

[RainLover]

Splitting Database is the area which I have to dig it likely more...

There is a wizard in Access 2003 that does this for you. I would assume that the same applies in 2010.

Would you recommend to use old .mdb format due it has "Group & User Permissions" feature?

I had the assumption that you were using Version 2010, MDB implies 2003 or earlier. If you could enlighten me then that would help.

I would suggest NOT to use "User Level Security". It has been phased out in later versions so it will eventually cause you problems. Also it is not that simple to use and maintain. You could write your own security forms etc better.

How far do you want to go with this security. Advanced programmers would most likely be able to break through your security. So are you just trying to keep the honest people out. If this is a serious requirement then you should be using a different back end for a starter. You should also consider hiring someone with security experience.

One of the most simplest things to protect Data is to put a Password on the back end. But don't tell the users what it is. The system will remember the password each time it is opened. So all access to the data must be via your forms etc not by some 3rd party program.

Hope this helps some more.

 

[Sombrero]

I had the assumption that you were using Version 2010, MDB implies 2003 or earlier. If you could enlighten me then that would help.

If you open .MDB DB in later 2003 access version the function of "User Level Security" settings are still present and can be managed, although ACCDB is the default DB in my case for 2010 ! it can be can converted to MDB format...

How far do you want to go with this security. Advanced programmers would most likely be able to break through your security. So are you just trying to keep the honest people out. If this is a serious requirement then you should be using a different back end for a starter. You should also consider hiring someone with security experience.

As far as possible within the limitation of access DB, by applying different layers & technics level which reduce the risk to the minimum...

Very much appreciated for your tips...

Thanks & Best Regards...

 

[RainLover]

That is all the generalised help I can give.

If you have any specific questions try asking them in a separate and new thread.

Good luck.