Sample data · this browser only
Incidents
A workplace book: incidents at a location, with parties and
disciplinary actions. Combos store IDs. Startup is fmnuMain.
Open hides inactive incidents.
| ID | Title | Occurred |
|---|
Incident
Save this incident first. The Parties tab stays grey until then — waiting, not broken.
| Person | Role |
|---|
Save this incident first.
| Person | Date | Verbal |
|---|
| ID | Name |
|---|
Person
| ID | Name |
|---|
Employee
What this demo shows
A Microsoft Access workplace incident book in the browser: incidents, parties, and disciplinary actions.
- Not Issues / Bugs — those are generic trackers. This is a plant incident with location and parties.
- Not Complaints — those are member complaints. People live in
tblIncidentPerson. - Open filter — hides inactive incidents.
- Child tabs — parties and actions idle until the incident is saved. Combos store IDs.
- Assignees are employees —
tblEmployeesmatches Time Card. - Unsaved changes — Yes / No / Cancel before leaving a dirty record.
Will this work when the data is in a database?
Yes. Incident, person, party, and action rows are separate tables with FKs. File links, the source checkbox-types sheet, and shifts are omitted this pass.
Sample data only. Source: Incidents on access-diva.com.