Input request for designing a db

Hello everyone,
I am a hobbyist, amateur programmer. A friend of mine runs a small trucking company with around 5 trucks. He does all his work on excel sheets and has been doing this for years. I offered to build a small desktop database app for him.
I am still at the initial stage of designing the database tables. I am kind of stuck at the concept of a 'Trip'. The way my friend does is: once the truck is out with a load, and till it returns back to the yard, that he terms as a trip. He assigns a single Trip Number to this. And when he pays his drivers he makes the salary based on the same logic. So an example of the trip:

Trip1 by user70 posted Jan 21, 2017 at 3:12 PM

another example is this:

Trip2 by user70 posted Jan 21, 2017 at 3:12 PM

But I asked around and some companies do like this:

Trip3 by user70 posted Jan 21, 2017 at 3:12 PM

And:

Trip4 by user70 posted Jan 21, 2017 at 3:12 PM

So my question to you experienced people is, what is the standard way of doing this in the industry? How does your company assign trip numbers? The 2 different type of Trips would demand very different DB tables.
Thank you in advance for all your input. It would be highly appreciated.

 

Whatever do you mean by this? Are you suggesting that I do not know how to design db tables? And how did you come to this conclusion? I don't know if you know anything about db tables but if you do you should know that a programmer tries to mould software logic after the real world.
Its easily possible to consider a pick and drop as a single trip and treat this as single row. On the other hand its also possible to treat multiple pickups and drops as being part of one single trip. It would be the decision of the business how it wishes to assign trip numbers and what constitutes a 'unit' in their job. A programmer can do it either way and no way in wrong for him.
Your statement about "where did I learn about tables" seems to imply that somehow a db designer would automatically know what a 'trip' is composed of. Going by that logic maybe a programmer should know everything of all other industries in the world then? Right?
I do not know you but your comment seems to suggest that you yourself do not know much of databases. This is brought out by the fact that you think that knowing database tables would automatically bring a deeper understanding of what trips are in the truck industry and how drivers fill in trip sheets and how trip numbers are assigned by the dispatch office and how records are maintained in a trucking office.
That is strange and laughable.
A programmer comes to the design by trying to understand the current industry standards. It would be foolish to impose personal ideas on a new project without understanding how the industry functions.

To take the case on hand, my friend does it one way. But i found out that others are doing it in another way. Now I wanted to understand a clear picture before making a decision. This decision would not only affect my design BUT also HOW MY FRIEND RUNS HIS SYSTEM. Because he would have to change things the way he has been doing uptil now.

 

Thank you for your reply. That's what, I found out, was being done in a company outside. Your reply corroborates that. Thank you.

 

Maybe the way i posted my original question was not clear so I just want to clarify that my query had nothing to do with 'how to design my database'. Thats my part and i can do it very well.
My query is to find out about how something is being mostly done in the industry.