Sample data · this browser only
Complaints
A handling-company book: members (company or contact in one table) and their complaints,
with activities and levies. Combos store IDs. Startup is fmnuMain.
Open hides inactive complaints.
| ID | Title | Reference |
|---|
Complaint
Save this complaint first. The Activities tab stays grey until then — waiting, not broken.
| Type | Date | Done |
|---|
Save this complaint first.
| Levy | Amount |
|---|
| ID | Name |
|---|
Member
Save this member first.
| Fee | Amount |
|---|
| ID | Name |
|---|
Employee
What this demo shows
A Microsoft Access complaints book in the browser: members (company or contact in one table), complaints, activities, and levies.
- One member table — a company has no parent; a contact sets
AttachedToMemberIDto that company. - Not Issues / Bugs — those are generic trackers. This is complaints for members.
- Open filter — hides inactive complaints.
- Child tabs — activities and levies idle until the complaint is saved. Member fees idle until the member is saved. Combos store IDs.
- Handlers 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. Member, complaint, activity, levy, and fee rows are separate tables with FKs. State catalogs and the full associate HR profile are omitted this pass.
Sample data only. Source: Complaints on access-diva.com.