Access includes a built-in User-Level Security system to allow you to create
userid and passwords then to assign specific privileges to every object in
your database.
Don't reinvent the wheel, use the tools available. Using your home-grown
security has tons of holes. What keeps the user from simply opening the
table and bypassing your form altogether? What prevents them from going
into design view and reading your code?
Read and reread the following links, make a backup copy of your files, then
follow every step in order.
Security FAQ
http://support.microsoft.com/?id=207793
The Security Whitepaper is also worth reading to help you understand.
http://support.microsoft.com/?id=148555
Joan Wild:
www.jmwild.com/AccessSecurity.htm
Lynn Trapp
http://www.ltcomputerdesigns.com/Security.htm

Signature
Rick B
> Hello,
>
[quoted text clipped - 20 lines]
> Thanks,
> Justine
JNariss - 13 Dec 2005 18:18 GMT
Rick-
I really appreciate your quick response. However, here is the problem:
I don't have the time to set up security right now. My boss's boss
needs this done today by 3 and I don't really have the time to set up
each users security. So that is why we came up with the code dialog
box. I will eventually set up security but right now we just need it on
this one form.
Thanks,
Justine
Rick B - 13 Dec 2005 18:23 GMT
If it is temporary and you know it will not be very secure, then just get
rid of the table and do it all in code.
Set the form or file to locked.
Ask the user to enter the password.
If the password equals snow, unlock the form.
Otherwise, loop.

Signature
Rick B
> Rick-
>
[quoted text clipped - 7 lines]
> Thanks,
> Justine
Rick B - 13 Dec 2005 18:29 GMT
Or just build TWO userIDs for the moment. One that has access to the form,
and one that does not.
Then, later go back and add the rest of your users.

Signature
Rick B
> Rick-
>
[quoted text clipped - 7 lines]
> Thanks,
> Justine
JNariss - 13 Dec 2005 19:44 GMT
Thanks Rick,
I will try to do the lock form method. I really appreciate all your
help.
Justine