If it appears that the code is fine and it's something else in my database please let me know so I can go elsewhere for help in finding a solution. Like I said at this point I'm wondering if my problem is even in my code or if it's related to my relationships. I omitted everything else that was working. I apologize for this being over 20 lines, but I wanted to make sure I got my entire elseif statement in. RstTime("LName") = DLookup("", "EmployeeInfo", strSQL) RstTime("FName") = DLookup("", "EmployeeInfo", strSQL) 'Create a new record because this will be the first entry done of the day in the tableĮlseIf Me.PasswordEntry = str_foundPW Then MsgBox "Incorrect Password.", vbOKOnly, "Required Data"
MsgBox "You must provide your password.", vbOKOnly, "Required Data"ĮlseIf Me.PasswordEntry str_foundPW Then
If Me.PasswordEntry & vbNullString = "" Then Set rstTime = dbsFloor.OpenRecordset("TblTimeSlip") Anyway any insight possible is greatly appreciated and I'm sure its some simple thing I'm overlooking. I'm wondering if it has to do with my relationships and the way they are setup. There are no fields in the employee information table that are required. I'm very confused as to what this is getting at. You cannot add or change a record because a related record is required in table 'Employee Information'.
#Use access runtime 2010 to upgrade update#
When it tries to update the database it throws the error Run-time error '3201':
They click Clock in and it will automatically create a new record and fill in their employee id, first name, Last name, The date, and the time of clocking in. The person selects their username from a dropdown menu and proceeds to enter their password in the textbox. When the employee opens the form they are given a combobox (UserNameSelect), a textbox (PasswordEntry) and 4 command buttons: cmdClockIn, CmdLunchOut, CmdLunchIn, CmdClockOut. I just got some fantastic help here earlier so I hope for the same luck. so try to break it down as much as possible. Keep in mind that I'm new to VBA with access.
0 kommentar(er)
