Sample data · this browser only
Vehicles
Canonical tblVehicles / tblExpenses.
Startup is fmnuMain: Vehicles or Expenses.
Expense Type stores ExpenseTypeID and shows the name.
Click a row. Expenses below follow VehicleID like the Access subform.
| ID | Make | Model | Reg |
|---|
Vehicle
Make and Model required. Mark Sold sets Active = No.
Expenses (fsubExpenses · this VehicleID)
Child rows for the selected vehicle.
| ID | Date | Type | Description | Cost |
|---|
Open expenses (frmExpenseList)
Click a row. Type combo stores ExpenseTypeID.
| ID | Make | Model | Type | Description | Cost |
|---|
Expense
What this demo shows
A Microsoft Access fleet register in the browser: vehicles, expenses, and a type combo that stores the ID.
- Switchboard — startup
fmnuMain: Vehicles or Expenses. - Parent / child — expenses follow
VehicleIDlike an Access subform. - Combo stores the ID — expense type saves
ExpenseTypeID, shows the name. - Mark Sold —
Active = Nowithout deleting the vehicle. - Unsaved changes — leave a dirty record and you get Yes / No / Cancel (Access
Me.Dirty).
Will this work when the data is in a database?
Yes. Sample rows live in this browser. The same keys and combo IDs are what a company database would store; only the save call would go over the network.
Sample data only. Source: Microsoft Access Vehicle Maintenance template.