Creating User Names and Password for Mutliple users

nyrob609

Registered User.
Local time
Today, 15:57
Joined
May 22, 2009
Messages
46
Hi All,

I need everyone expertise...I have a database with multiple forms that is currently use by 10. This will increase in next month to 50 the database is on shared drive. The database has been deleted twice in the last two weeks and IT had to restore the database.

I would like to set up user names and passwords for all the users as well as set up permissions on what to view. I would like for me to be the admin and everyone else be user with data entry only on the forms, view, print reports. Also track who is login into the database.

How do I create a listing of multiple users and passwords???

I also would like to avoid losing data because somebody deletes the database would I use the function of splitting the database so that I house the real database in my personal drive and have the switchboard, and forms on the shared drive.

Your suggestions are greatly appreciated.

Thank you
 
well what you want is a whole lot :P

basically, when you want them to not be able to delete the database, you have to put the back end of the database where they can't access it, cause they're only supposed to use the front end anyway.

in regards to entry deletion at the interface, that depends on how you set your database up, like let's say, user level 1 has administrative power over all forms while a data entry can only enter data then needs permission to edit it.

perhaps you can show a screen shot of your database or something so people here would have an idea, but what your asking is a massive undertaking though.
 
There is a problem with trying to keep them from deleting the database. If you want the database to be read only then you can remove delete permissions from the folder where the backend is kept. If you want people to be able to update information and add data or delete data, then you cannot limit their Access to the backend - period.

I believe this is more of a process issue and management issue. IT should be able to determine which user login deleted the file. Management should step up and tell people that if they delete that file they risk immediate termination along with letting people know that they can figure out who did it. And if someone comes along to an unsecured workstation (meaning logged in but not locked while someone isn't in front of it) then the person who has that unsecured workstation will be the one taking the fall, so lock your PC if you step away.

So, the only other guaranteed way is to move to SQL Server or SQL Server Express so that you can keep the data files where they can't go.
 

Users who are viewing this thread

Back
Top Bottom