Sample data · this browser only
Rentals
Rental property management: properties, units, and guests.
A building sits under a property. A booking puts a guest in a unit.
Startup is fmnuMain.
| ID | Name | City |
|---|
Property
Save or select a property first, then add a building.
| Building | Type |
|---|
| ID | Unit | Property | Rent |
|---|
Unit
Save or select a unit first, then add a booking.
| Guest | Start | Status |
|---|
| ID | Name | Company | Phone |
|---|
Guest
What this demo shows
A Microsoft Access rental book in the browser: a property, its buildings and units, and guests booked into those units.
- Not Real estate — that slug is
tblProperty/ tenant / lease. This istblRentalProperty→ building → unit → guest booking. - Buildings child tab — idle until the property is saved.
- Bookings child tab — idle until the unit is saved. Combos store IDs.
- Unsaved changes — Yes / No / Cancel before leaving a dirty record.
Will this work when the data is in a database?
Yes. Property, building, unit, guest, and booking are separate tables with FKs. Parking, utilities, photos, and move-in inspections from the Access Diva model are omitted this pass.
Sample data only. Source: Property Management on access-diva.com.