Many to many relationships

[TriMetric]

Trying to make a vehicle maintenance log.

In the attached have I done things correctly? or should I have done it differently?

I made the tables based on physical paper records, in the database I'm thinking the tblFuelFill and tblMaintenanceInformation can be combined or maybe the two inspection tables?

Structure, tblVehicleInformation will have a main form, buttons to open forms for filling in the other tables, tabs to display information of the other tables with some calculated fields.

In retrospect I guess tblDealer should have been named tblGarage.

Also, not sure how the junction tables will get populated?

Thank you,

Matthew

 

[jdraw]

Can you tell readers in 5-6 lines, simple English --no jargon -- what exactly is the the "business" you are trying to automate/support with database?

Forget tables etc for the moment ---just plain English.

There are some free, generic data models at Barry Williams' site--here is one
re Vehicle Maintenance

 

[TriMetric]

Can you tell readers in 5-6 lines, simple English --no jargon -- what exactly is the the "business" you are trying to automate/support with database?

I'm not trying to support a business. I'm more interested tracking a closer actual cost of owning a vehicle. Also, getting a wearable parts (ex. brake pads) replacement timeline, all for better budgeting.

This will also be a stepping stone to improve some very basic access databases I use at work as they are just tables, I've already added forms to each, yes, I'm permitted to modify them.

Matthew

 

[jdraw]

You've taken "business" too literally. Your response suggests that your "business" (or the purpose of your proposed database/application) is the collection of information regarding the costs associated with owning a vehicle.

This free, generic model may help with setting up your design.

Good luck.