Why are member names stored into other tables (Guest Tickets and Keys_issued_register) instead of member number? What purpose does Keys_issued_register table serve?
Strongly advise not to use spaces in naming convention. Also advise to give controls more meaningful names than the Access defaults.
Debug/Compile fails on procedures for buttons that don't exist.
New_key_register table has ID field defined as PK but Keyno is saved into Angling_details as FK. Designated PK should be saved as FK. Either set Keyno as PK or save ID into Angling_details.
Still trying to understand business processes. Since Angling_details appears to be a transaction table for keys issued and payments, under what circumstances would you want to do a bulk return of keys and set NEWKEY to null? Or since this button is not visible, is procedure not even used?
Why is year 2022 hard-coded in the SQL for IssuedKeys procedure? I ran this procedure for 2023 and I am confused by the KSEASON data. Value in New_key_register is not what is shown in sfrmKeys. Why is Chambers listed when their status is LAPSED? - other LAPSED were not included.
If you want to utlilize USED field to indicate keys that should not be assigned (for whatever reason - already assigned, lost), can certainly do that. However, the process to programmatically update that field when keys are issued/returned is what is not advised. Keys unavailable for issue due to assignment can be calculated but then if need to additionally restrict a key because it is LOST that must be identified somewhere. This brings to mind MS LendingLibrary template. Each book loan is a transaction with CheckOut and CheckIn data. If CheckIn field is null book is out and not available. If asset is removed from inventory (lost, sold, destroyed) a date field in Assets table indicates such.