M
Martin Hopkins
Hello,
I currently have an Access 2000 database that is split front and backend
with many users accessing the front end from their personnel directories on
the server system.
Currently personnel are recorded onto the database by a system admin who
records their core details and assigns user roles. 90% are users and can
only see their record.
They open the database and "logon" into the database by beinbg prompted for
their work number which is then verified as part of a query and lets them
use the database in accodance with their assigned user role. If they have
not been entered onto the database then they get a blank logon screen
informing them to contact system admin. However this is flawed if someone
knows someone elses work number, they could access the database illegally. I
could use passwords etc but with 700+ users I think this could be long
winded, unless there is a way of personnel creating a password when they
first log into the systen and that being stored in the table for future
reference to verify when logging on
Anyway, what I would like to do is, if possible, is to use the users windows
logon name, which includes the work number, and verify this against the
recorded details on the database. e.g Windows user name Mr P Smith Work
Number 1234567 can access database because he is in the employess table.
Any help creatly appreciated.
Martin Hopkins
I currently have an Access 2000 database that is split front and backend
with many users accessing the front end from their personnel directories on
the server system.
Currently personnel are recorded onto the database by a system admin who
records their core details and assigns user roles. 90% are users and can
only see their record.
They open the database and "logon" into the database by beinbg prompted for
their work number which is then verified as part of a query and lets them
use the database in accodance with their assigned user role. If they have
not been entered onto the database then they get a blank logon screen
informing them to contact system admin. However this is flawed if someone
knows someone elses work number, they could access the database illegally. I
could use passwords etc but with 700+ users I think this could be long
winded, unless there is a way of personnel creating a password when they
first log into the systen and that being stored in the table for future
reference to verify when logging on
Anyway, what I would like to do is, if possible, is to use the users windows
logon name, which includes the work number, and verify this against the
recorded details on the database. e.g Windows user name Mr P Smith Work
Number 1234567 can access database because he is in the employess table.
Any help creatly appreciated.
Martin Hopkins