custom log-in

[Parasyke]

Can anyone coach me in a custom log-in screen? I have a table set up
with users and a password. I don't need high-level security, just the
ability to recognize the stored user without API calls and genuine
MS-Access security (just don't want to implement workgroups at this
time). So basically the user sign in form would authenticate the user
and password (IF - Then) and store that value in a hidden form that
would remain open but invisible. Then I could reference the
Forms!Logon!Textbox value stored (but if I have multiple users that's a
problem (?)). What I ultimately want the stored value to do is allow me
to pass it into some queries for filtering reports and displays.
Any ideas? Thanks in advance!

[Rick Brandt]

Parasyke wrote:

Can anyone coach me in a custom log-in screen? I have a table set up
with users and a password. I don't need high-level security, just the
ability to recognize the stored user without API calls and genuine
MS-Access security (just don't want to implement workgroups at this
time). So basically the user sign in form would authenticate the user
and password (IF - Then) and store that value in a hidden form that
would remain open but invisible. Then I could reference the
Forms!Logon!Textbox value stored (but if I have multiple users that's
a problem (?)). What I ultimately want the stored value to do is
allow me to pass it into some queries for filtering reports and
displays.
Any ideas? Thanks in advance!

You've pretty much described the whole thing and no, multple users would not be
a problem. What part of what you've outlined above are you having problems
with?

Use DLookup() to test the UserName and Password entered.

Use Me.Visible = False to hide the form.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Bob Quintal]

"Parasyke" <kr************@yahoo.comwrote in
news:11**********************@b28g2000cwb.googlegr oups.com:

Can anyone coach me in a custom log-in screen? I have a table
set up with users and a password. I don't need high-level
security, just the ability to recognize the stored user
without API calls and genuine MS-Access security (just don't
want to implement workgroups at this time). So basically the
user sign in form would authenticate the user and password (IF
- Then) and store that value in a hidden form that would
remain open but invisible. Then I could reference the
Forms!Logon!Textbox value stored (but if I have multiple users
that's a problem (?)).

that's not a problem. since the form is not bound to a table,
the value in one instance of access is invisible to the other
instances of access.

What I ultimately want the stored value

to do is allow me to pass it into some queries for filtering
reports and displays. Any ideas? Thanks in advance!

I create an unbound form that contains several labels and one
button. The form is on a timer that opens the main menu form and
makes the welcome form invisible, then sets the timer interval
to 0. The button just executes the On timer event.

I load several pieces of data into the labels' caption
properties in the startup code, such as the machine ID and User
name. The welcome form will show "Good morning, Parasyke" and "
Welcome to the Whatchemecallit database"

Just use the login form and make it invisible after the user has
passed the login password test you create.

--
Bob Quintal

PA is y I've altered my email address.

--
Posted via a free Usenet account from http://www.teranews.com

[Parasyke]

Any code snippet on how to use the DLookup() (I'm assuming stored in
the form's SQL rather than a separate query?).... Thanks!

Rick Brandt wrote:

Parasyke wrote:

Can anyone coach me in a custom log-in screen? I have a table set up
with users and a password. I don't need high-level security, just the
ability to recognize the stored user without API calls and genuine
MS-Access security (just don't want to implement workgroups at this
time). So basically the user sign in form would authenticate the user
and password (IF - Then) and store that value in a hidden form that
would remain open but invisible. Then I could reference the
Forms!Logon!Textbox value stored (but if I have multiple users that's
a problem (?)). What I ultimately want the stored value to do is
allow me to pass it into some queries for filtering reports and
displays.
Any ideas? Thanks in advance!

You've pretty much described the whole thing and no, multple users would not be
a problem. What part of what you've outlined above are you having problems
with?

Use DLookup() to test the UserName and Password entered.

Use Me.Visible = False to hide the form.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com