I agree that setting Lookups in table is annoying, I NEVER do that. However, using lookup alias in combobox on form is another issue.
I agree that setting Lookups in table is annoying, I NEVER do that. However, using lookup alias in combobox on form is another issue.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Here is the database, I would assume that the lookup fields may be the reason why I am having issues, but I don't know what to do to achieve the same result and not use them. Please feel free to educate me since I am learning as I go through this?Crossing Guards.zip
You can use lookups in comboboxes and listboxes on form. It's just setting them in tables is annoying. If you do use lookups have to make sure to set the BoundColumn property to the correct field and reference the appropriate column in any code that uses the combo/list box if you want something other than the BoundColumn value.
The only place I see a 'lookup' is the GuardName combobox on frm_tbl_cg_shifts. The RowSource for this combobox includes a field called GuardName but there is no such field in tbl_GuardInfo. There is a GuardName field in tbl_cg_shifts. Fix the combobox.
The date_worked field in tbl_payroll_shifts is a text type, should be Date/Time.
The criteria under the School field in the UPDATE query doesn't make sense. Should not be a field in the query, should be some input by user.
Criteria under the date_worked field in the UPDATE query should be: Between #10/14/2012# And #10/27/2012#
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.