Prompt for password and username each time while pressing cmd button

[Angeluz]

Being dealing with my database and having quite some trouble with it. Is it possible to track down what the users did, during the time they login into, database, is it possible to prompt users for password and username when they buttons for like, delete cmd, or update command.

Just a breif idea on what im trying to do.(hopefully it won't confused you all)
Im trying to created a 2 main username. One is for admin group and another is for users group. Then users can login in to database, however whenever the users update or delete entries in the database, the user will prompt for their username and password (not the users group login ). Is it possible to build a table to store in the username and password for the prompting purposes one.

Sorry for confusing question. Actually im trying to think of another way, but for now this complicated event all i have think of. Feel free to voice your suggestion here. Thanks alot. TQ

 

[The_Doc_Man]

Look up InputBox as a way to engage a user in a dialog. Look up "MODAL" as a parameter that says (in effect), "Answer this question or lose use of your computer." A modal Input Box for username and another one for password would do you well. There is also a way to make the password box not echo anything or echo asterisks, though you will have to look that one up. It has been too long since I've played with such a thing,

As to building a table for history, or having a table for validation, yes. But remember that someone with a copy of Access can write something to look into your other database tables if you are not careful in how you secure the DB file. So passwords could easily be divulged.

You won't like my next comment: Your approach to security is an "I don't want to bother doing it right" approach. The ONLY way to assure individual validation with Access without having to reinvent a LOT of big, whompin' wheels is to use Workgroup Security correctly. Or spend money on some third-party add-in that might or might not do what you wanted. You can search the forum for lots of threads on the subject of Securing a DB.

 

[Angeluz]

Sorry doc Man, i don't understand you, starting from the phase that "you won't like my comment". Are you telling me that my way is wrong. Well i feel the same also actually, but currently that what i can think of. Because as my users are changing very frequently, (my users are usually hire for limited amount of time, mostly contract basis, abt 6 months), so i think i will be easier to change passwordby directly changing it in the table.
Any better ideas, im scratching my head now..

 

[Moniker]

Err, look at this...

You should be able to adapt that to your situation without too much hand-holding.

 

[Angeluz]

Moniker I great great thank you for all your help. I am slow to learn i must admit but you really aid me alot. thanks a bunch.