As I mentioned:
?ctl.Name
tabGInstrCertifications
that refers to a specific page of your tab control, which does indeed have "Audit" in the tag property.
I found that error in the Immediate Code window per your helpful advice and removed the Audit tag and still got the same error from my original post. Unless I somehow missed a field, all of the audit tags have been removed.
Don't have that VM running right now, but from memory each certification is a field, right? I would have them in a related table, where each record represented a single certification for a person. Here's the tipoff: when they implement a new certification, will your application handle it without you having to redesign tables, forms, reports, etc? A normalized db would.
It may well be too late to change it, I just wanted to point it out.
Thank you for pointing that out to me. I do understand the general idea of normalization from my college days, but for my current needs, I only require a table that lists expiration dates for various certifications. My current structure seems to satisfy that need. Here is the big picture:
Purpose: To hold information about a staff member's certification status in order to run reports and send out notifications.
Information kept for staff members:
Name
ID #'s (for tracking in different agency systems)
Job Status (active, sick leave, etc.)
Certifications (expiration dates and status [current/expired])
Notes (anything that explains something not referenced in a field)
When a new certification is implemented, my plan is to add a new field to the table. I would then need to add a new update query, report and redesign the form that contains the listing of all certifications.
I'm not sure I understand how a normalized db would prevent me from needing to add new queries, reports and redesigning forms when a new certification is implemented. Perhaps you could elaborate when you get a chance?
I am open to making changes, but I am also working under time constraints. Thanks again!