Paul,
A Form is where one enters data.
A Report is where one views data.
So... The reports you need to make are one for each SET of data you want to see at one time.
I already made an Estimated Pay, because I know that when I worked for hire, I always wanted to have an idea how much i had earned so far.
I kinda, sorta, showed a payslip, so one could compare paid hours, etc, to actual worked hours, etc, because paymasters make mistakes. I don't know enough about he UK to make anything resembling what works over there.
I know that you will want a Work Schedule that shows at least the last weeks actual work and the upcoming work planned as far as the boss/dispatcher can tell you, along with any approved holidays. This Report must let the driver know what hours he is restricted to and should let him plan his days off.
There are two species of Reports; What a driver needs to know and what are nice to know. Since your time to complete this App is growing short, concentrate on what he needs to know. It won't be a problem to add any more Reports later. In fact it will be quite easy and you probably won't even need my help after you've seen how to do it once.
The Reports finalize the Databases and the Databases finalize the Forms. Even after the App is put into production it is easy to add to if it is properly designed.
You've told me that a driver needs to know how many 9s and 11's he has left in this period, so that when dispatch tells him to take a load of coal to Newcastle, he can say, "hey, that's an 11 hour trip, and I've used mine up." That is a "need to know" report. The "Estimated Pay" Report is a "nice to know" Report. I only made it because it's the only Report I CAN make for you. I just don't know anything about driving in the UK. Well, I do know that you drive on the wrong side of the road.
Keep the Report simple and to the point. A driver doesn't need to know how many 9s and 11s he worked last week, he does need to know if he can work one today. He doesn't need to know how many holidays he has taken, he needs to know that he has one tomorrow.
Paul, consider your official drivers log. When you need information from it for some reason, what information is it that you need? Those bits of information are "need to know" Reports
There is probably a couple of situations that make you look in the log. Each situation probably makes you look at some different information than the others. Those situations are different Reports. Different Reports can have the some bits of the same information on them. That's how you know if you should combine two reports; if most of the bits are the same and only a few bits are different, then combine them. But if most of the bits of information are different, then they should be separate Reports.
I notice that you are still talking about. There are no weekly and fortnightly and monthly anything. Code will expand the generic (Weekly by design) whatever into the period required. Design them with 7 days and let code do the rest. It is simple code.weekly/fortnightly/monthly or Agency timesheets
Paul, you are running out of time. Let's concentrate on delivering a very simple App that only does what a driver needs to know.
This is why I say that:
Designing an App that has one form and two reports takes as much time as adding three more forms and 10 more Reports.
If it is very simple, you won't feel bad about giving it to 5 or 6 of your mates for Beta testing and promising them that if they are good beta testers, they can get the updates gratis. You do not want to be selling anything that has not been Beta tested, because it will ruin the reputation of your App forever.
A good Beta tester:Actually uses the App;
Promptly tells you when you App errors;
Tells you what they don't like about the App;
Tells you what they do like;
Tells you what additional features they would like to see.
