So, you know what you want to do. How far are you getting before you're stuck?
Consider also, that in most systems nowadays you already have account information in as much as the user must log on to their system before they can get access to the database. This information is always available (
Function to Return UserName (NT Login) of Current User) so it nearly always makes sense to use that instead of trying to roll your own.
If you really
must roll your own then at the very least you should make sure that the passwords are
never stored in plain text. That's criminal behaviour. I actually mean that. Almost. In some instances it actually can be considered criminal as it exposes users' passwords to those who would use the information for further criminal acts. This affects more than just those systems you're responsible for as users often use the same passwords in multiple systems. Hence the possibility of exposing yourself to criminal prosecution unless you can show you've taken reasonable measures to prevent that. An Access database with passwords stored in plain text is certainly not an example of reasonable measures.
OTOH using O/S accounts saves you all that hassle as well as being a lot more reliable.