Simplified form by login module

[Tindan]

I wonder of i can simplify the client form by reducing ceritain field, but still stored to the records.
For example, i give assignment to review a book to 30 students, and i want them to report using access.
The first module Will be login page, and after login they Will be directed to the same form, but on that form, they don't have to input their name, classes, and student number anymore because itu itu Will be gathered by their login id. (I add name, classes, and student id fields on the login table). Anyone can help?

[NeoPa]

Have the students already logged onto the computer/domain when they run this Access application? Or do they share a system?

I ask because most people starting out believe they need the operator to sign in again. Into the Access application. In most cases that is both unnecessary and introduces many security problems. Problems you really don't want to be responsible for introducing.

You can retrieve the UserID of the operator from within Access (See Function to Return UserName (NT Login) of Current User). You can store information for each supported user in a local table to handle who can do what. The Primary ID of that table (obviously) would be the UserID you've got from the OS.

An example of such usage, albeit fairly full-featured, can be found at How To Create User Permissions and Customized Menus in MS Access. Bear in mind that's just one example. It can provide you with a number of ideas for your project, but do make sure yours fits what you want/need.

Avoid user login forms like the plague. They can be almost as damaging to you in their own way.

[Tindan]

I'll check it. Wil let u know soon