Should I use a one to one relationship?

[Stephenson]

Hello all,

I'm building a DB that in addition to other needs will record the use of construction equipment. Service/maintenance is a great requirement of my db, therefore gathering the current use (hours/miles) will be gathered in many forms. I would like these forms to both display as well as intake the most current use of the equipment.


I am not accustomed to using one to one relationships, but this instance has made me think I would be best off using this relationship. If I'm incorrect please tell me the best way to handle this data. If I am correct please instruct me on the best way to setup a one to one relationship and utilize it as I have not done this before.

Thank you for taking a look,

John.

[orange]

Normally if you have a business rule that suggests a 1:1 relationship, the proposed tables can be reduced to 1 table.
However, if you have equipment that can be serviced or have multiple "Maintenance Events", it would seem to be a 1 to Many relationship.

Consider, BackHoe X was acquired on 7 March 2016; had its 50 hour checkup on 18 March 2016; had routine fluid check on 23 April 2016 and is scheduled for filter changes on 14 May 2016.

My example may not match your set up.
Here is a free data model from Barry Williams' site that may give you some insight.

Good luck with your project.

Good luck.

[Stephenson]

Orange,

Thank you for your insight and the link. I think you're correct in that it should be a one to many relationship.

I will give it a shot.

Thank you.

[Stephenson]

I'm setting up the relationships and tables for my equipment module. In addition to not knowing the best way to lay out all the tables and relationships I'm unclear on the best table to store the Equipment use amount field (hrs./miles) as well as how to relate it to my other tables.
I would like the user to have the opportunity to enter the use in many forms so I'm sure to capture the most recent record.
Please let me know if you have a good idea of where to hold this field or any other suggestions on my tables and relationships.






Thank you for taking a look.