Re: Generic Password

Does this question have anything to do with my previous post? I did not
recommend anything to do with an Input Mask.

Did you post this to your previous thread by mistake?


--
Rick B



"jsc3489" <jsc3489@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B7F04D66-87B9-48A8-8658-6134FBA60D86@xxxxxxxxxxxxxxxx
> There's only one problem with that. I goto the "..." after Input Mask and
> an
> error says "Microcrap Access can't start the wizard. This feature is not
> currently installed blah blah blah". It can't find the Office1.cab that it
> thinks should be on my desktop?!?!?
> Unless there's another way?
> --
> I reject your reality and substitute my own.
>
> Promote hydrogen - one of the best "clean" fuels there are!
>
>
> "Rick B" wrote:
>
>> If it were me I would not try to reinvent the wheel. Use the built-in
>> User-Level Security. After the user logs in once, they will have access
>> only to what they should. You will be able to use the UserID to filter
>> records so they can only see their own. You can even default in their
>> userid or name when they create a new time card.
>>
>> If it were me, I'd undo all the home-grown security you've built and
>> simply
>> use the built-in security.
>>
>> You should make at least one backup, then read and reread all the
>> instructions, then dive in. You must follow ALL the steps IN ORDER or it
>> will not work.
>>
>> Good Luck.
>>
>> 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
>>
>>
>> --
>> Rick B
>>
>>
>>
>> "jsc3489" <jsc3489@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:CF40F98C-34F9-4907-8E6C-EE22D650565A@xxxxxxxxxxxxxxxx
>> > I'm two weeks old with Access so be gentle.
>> >
>> > I'm trying to create a generic password system for a working time***
>> > form
>> > I have. I don't need high security, I just need to keep the employees
>> > filling
>> > out their own time*** instead of accidently someone elses.
>> > There are 18 employees at my company.
>> >
>> > This is my Form_Login code so far:
>> >
>> > ---------------------------------------------
>> > Option Compare Database
>> > Option Explicit
>> > ---------------------------------------------
>> > Private Sub Cancel_Click()
>> > DoCmd.Close
>> > End Sub
>> > ---------------------------------------------
>> > Private Sub Submit_Click()
>> >
>> > Dim stDocName As String
>> >
>> > stDocName = "Password"
>> > DoCmd.OpenForm stDocName
>> >
>> > Exit_Submit_Click:
>> > Exit Sub
>> >
>> > Err_Submit_Click:
>> > MsgBox err.Description
>> > Resume Exit_Submit_Click
>> >
>> > End Sub
>> > __________________________________________________
>> > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> > ----------------------------------------------------------------------
>> > This my From_Password code:
>> >
>> > ---------------------------------------------
>> > Option Explicit
>> > ---------------------------------------------
>> > Private Sub Form_Load()
>> >
>> > gOkToClose = False
>> > ' number of tries
>> > gintPasswordFlag = 1
>> >
>> > End Sub
>> > ---------------------------------------------
>> > Private Sub Form_Unload(Cancel As Integer)
>> >
>> > If Not gOkToClose Then
>> > Cancel = True
>> > End If
>> >
>> > End Sub
>> > ---------------------------------------------
>> > Private Sub PASSWORD_AfterUpdate()
>> > On Error GoTo err_PASSWORD_AfterUpdate
>> >
>> > Dim strName As String
>> > Dim strPassword As String
>> >
>> > strName = Forms!login1.Login
>> > strPassword = Me![Password]
>> >
>> > If StrComp(Nz(DLookup("[Password]", "UserDef", "User_Name ='" & strName
>> > &
>> > "'"), ""), strPassword, 0) = 0 Then
>> > gOkToClose = True
>> > Dim Employee
>> > Employee = Forms!login1.[Login]
>> > DoCmd.Close acForm, "Login1"
>> > DoCmd.OpenForm "Time***", acNormal, "", "", acAdd, acNormal
>> > Forms!time***.SetFocus
>> > Forms!time***.Employee = Employee
>> >
>> > DoCmd.Close A_FORM, "Password"
>> > Else
>> > ' three tries
>> > Select Case gintPasswordFlag
>> > Case 1 To 2
>> > DoCmd.Beep
>> > MsgBox "Incorrect password", 16, "Password"
>> > gintPasswordFlag = gintPasswordFlag + 1
>> > Case Else
>> > DoCmd.Beep
>> > DoCmd.OpenForm "Fail"
>> > End Select
>> > End If
>> > exit_PASSWORD_AfterUpdate:
>> > Exit Sub
>> >
>> > err_PASSWORD_AfterUpdate:
>> > MsgBox "Error " & err & ": " & Error$, 0, "Password"
>> > Resume exit_PASSWORD_AfterUpdate
>> >
>> > End Sub
>> > ---------------------------------------------------------------------
>> >
>> > Most of this code I got from very helpful people on here.
>> >
>> > My biggest problem is designing my tables to work with this code.
>> > I've been given suggestions to create Table_UserDef to hold Passowrd
>> > info
>> > and reference Form_Login that has a dropdown of Employees and use the
>> > Dlookup
>> > statement in my code. However, I'm confused of how Dlookup works with
>> > my
>> > tables and where to put the info in my tables Dlookup needs to work.
>> >
>> > How it (is supposed to) works:
>> >
>> > Employee clicks on Login.htm (I will have to create) and selects thier
>> > name
>> > from a dropdown list and clicks submit. A password box pops up and if
>> > correctlty entered, closes and the time*** Form pops up, ready for
>> > that
>> > employee to fill in date, hours, etc..
>> >
>> > I'm lost with the tables...please help.
>> > --
>> > I reject your reality and substitute my own.
>> >
>> > Promote hydrogen - one of the best "clean" fuels there are!
>>
>>
>>


.