Sample data · this browser only
Bugs
Microsoft Access Bugs: a defect register with a comment thread. Lookups store IDs. Open = Active and not Resolved or Closed.
Click a row. Comments for that bug are on the Comments tab.
| ID | Summary | Status | Pri | Due |
|---|
Bug
Combos store the ID. Details holds due date and resolution. Comments is this BugID only.
Save or select a bug first, then add a comment.
| When | By | Comment |
|---|
What this demo shows
A Microsoft Access bugs register in the browser: lookups, an open filter, and a comment thread for the current bug.
- Not Issues — Issues is a ticket without a child table. This page has
tblBugComments. - Combo stores the ID — status, category, and priority save IDs and show names.
- Open filter — hides resolved and closed, like
qselBugsOpen. - Three tabs — Bug (who/what), Details (due, resolution, write-up), Comments (thread for this BugID).
- Mark Resolved — updates
StatusID, does not delete the row. - Unsaved changes — leave a dirty bug and you get Yes / No / Cancel (Access
Me.Dirty).
Will this work when the data is in a database?
Yes. The bug table holds the defect; the comment table holds the thread. A company database would use the same fields.
Sample data only. Source: Microsoft Access Bugs template. Login and Users are omitted this pass.