username and password for access

[AC-Dev]

Good Day all,

so here's the thing...I am using access 2010 and i want to password protect my database by user. there will be about 10-15 users(maybe that's just what I'm assuming). i want certain users to have access to everything, and certain users not to have access to one form which is brought up by a button called btnMaintenance. can someone advise? i would really not like to revert it back to access 2003 and use the user level security there (although it sucks that microsoft got rid of the function). Also, i want the users name to be displayed at the top of the swichboard saying "logged in as John Doe"

I was thinking to use a table to hold all the user information (name, employee ID,password) but im not thinking its too safe, unless there is a way to 100% guarantee the user cannot access the navigation pane in anyway

 

[GinaWhipp]

IMHO, the only real security is by using SQL Server. There is a free version...

http://www.microsoft.com/sqlserver/2008/en/us/express.aspx

...other then that you can implement your own using a form (you create), hiding the Navigation Pane and a password on your code BUT this does not keep the data safe from the savvy User.

 

[AC-Dev]

IMHO, the only real security is by using SQL Server. There is a free version...

http://www.microsoft.com/sqlserver/2008/en/us/express.aspx

is this a seperate development platform all together?

 

[GinaWhipp]

The only seperate would be you would store the tables with the data... The front end is still Access. Is that what you meant by seperate?

 

[missinglinq]

And for a multi-user environment, as the scenario given implies, you simply have to split the database into a Front End/Back End configuration. Tables with data goes into the Back End, which needs to be something like SQL Server or Oracle, with a single copy on a shared drive/folder, and everything else, Forms, Queries, Reports, Modules, etc, goes in the Front End. A copy of the Front End then goes on the hard drive of each user.

This is really not an option, but a necessity! Non-split Access apps, used in a multi-user environment, is a sure-fire recipe for repeated corruption/data loss! The really scary thing is that non-split files this can go for an extended period without problems, but once they arise, and they will, they will become chronic, causing data loss over and over and over again!

As with all matters of security, it all has to do with who/what you're trying to secure against. If you need a bicycle lock, your choice is guided by whether your bike is the Schwinn one-speed you got for your tenth birthday or a $5000 racing bike.

Are you protecting vital, proprietary business data, or simply trying protect the integrity of your objects designs? Are you securing against the casual data-entry personnel or against honest-to-god hackers?

Linq ;0)>

 

[AC-Dev]

The only seperate would be you would store the tables with the data... The front end is still Access. Is that what you meant by seperate?

i was wondering if that is a whole seperate development platform . so you mean once the db is seperated to front and back end, i would store the back end in that sql server?

 

[AC-Dev]

And for a multi-user environment, as the scenario given implies, you simply have to split the database into a Front End/Back End configuration. Tables with data goes into the Back End, which needs to be something like SQL Server or Oracle, with a single copy on a shared drive/folder, and everything else, Forms, Queries, Reports, Modules, etc, goes in the Front End. A copy of the Front End then goes on the hard drive of each user.

just a question. if a copy of the database must be stored on a shared drive, what purpose does sql server or oracle serve? can they not still attempt to access the copy on the shared drive?

Are you protecting vital, proprietary business data, or simply trying protect the integrity of your objects designs? Are you securing against the casual data-entry personnel or against honest-to-god hackers?

Linq ;0)>

i am simply trying to protect sensitive documents/materials. as for hackers, i dont think i have to worry about that. my company has a high-end line of security in our network and that is where i am storing the db.

 

[GinaWhipp]

i was wondering if that is a whole seperate development platform . so you mean once the db is seperated to front and back end, i would store the back end in that sql server?

That is correct...

 

[GinaWhipp]

Let's see if this helps...

The only reasons to use SQL Server is for security, database is too large for Access (close to 2 GIG) and/or you want to also interface with internet pages. (There are other reasons but for this thread this will suffice.)

In a multi-user or single-user I always recommend splitting. The back end which sits on the Server (whether it be SQL or not) will be backed up and there is little chance for corruption.

Whether split or not, unless using SQL Server with proper permissions it can be accessed by Users. To protect the front end, keep a master and distribute an .ACCDE to your Users. That way they cannot get at forms or code. A clever User can still get to the tables UNLESS using SQL Server with proper permissions. Now, if you cannot, for whatever reason, implement SQL Server then not muxh to go except hide tables and Navigation Pane and disable Shift Key. Please do all this on a copy as you will not be able to get to the database objects either and you may want to make changes.

This is no easy task to set up and your front ends must have the proper error handling or they will *crash* on all unhandled errors.

 

[AC-Dev]

thanks all for your help. i just downloaded the sql server and will try it out now.