J
Jason
Hello,
I have an access mdb front-end which i use for end-users. The back-end is
sql server 2000.
In the front-end there no linked tables or pass-through-queries, all
recordsources are binded in forms through ado.
At the moment i've created a login for the front-end to connect to the
database. This is hardcoded in a module, but i don't think this is best
practice.
Every form uses that connection to get data. So yes, the users won't have to
login. What i would like, is to have users log in but without creating extra
logins on sql server and still be able to know who's currently logged in.
How can i create a customized login form so that users can login into the
database. This login is not a jet-login in access.
Can anyone help me on this and if it is not best practice, please tell me
so.
I have an access mdb front-end which i use for end-users. The back-end is
sql server 2000.
In the front-end there no linked tables or pass-through-queries, all
recordsources are binded in forms through ado.
At the moment i've created a login for the front-end to connect to the
database. This is hardcoded in a module, but i don't think this is best
practice.
Every form uses that connection to get data. So yes, the users won't have to
login. What i would like, is to have users log in but without creating extra
logins on sql server and still be able to know who's currently logged in.
How can i create a customized login form so that users can login into the
database. This login is not a jet-login in access.
Can anyone help me on this and if it is not best practice, please tell me
so.