Paul,

That's as simple as it gets? Holey NewCastle Brown, Batman, no wonder you need to computerize your schedule.

Both those links are very helpful, I doubt I would ever have been able to code the schedule without the HGV Driver sheet.

I will be working on the Schedule, because that is going to need someone very familiar with VBA code to design.

so if i get this right then, for every tab on the userform you want me to create report or database on the spreadsheet?
No. You really need to look at your App from the perspective of a slow minded driver who just wants it to show him what he "Needs To Know" to be safe and legal. Those are the only Reports you need to think about right now. The rest will come after Beta testing.

I'll tell you a stupid trick I sometimes use, (because it really and truly works.) I collect ball caps and hats. I have one ball cap with the logo of an auto parts store; this is my Redneck Hat. My Redneck isn't the brightest bulb on the shelf. I put him on when I have a hard time getting into the slow and dumb mode to decide what needs to be in a Report, then I'll put on a rather stylish hat, (a sophisticated professional,) to see what nice things to put in. Only then will I start actually designing the Report (or UserForm.) When finished, I'll put the Redneck persona back on to make sure the new version doesn't confuse him.



Here's the reason you need to ignore the current UserForm: All the code on a UF needs to be in the same Code page. Even the simplest UF takes a couple of screens of code. Each Page on the UF takes a few more screens to see all the code. The code for the curent UF is going to take 4-5 screens per Page. It have 11 or 12 Pages, which means 40 to 50 screens of code. That is a lot of scrolling.

When we get to designing the Forms, we will have a Main navigation form with links to all the sub forms. Each sub Form will be based on one of the current Pages. Each sub Form will have three buttons at the bottom; Previous, Main, and Next, so the User can easily navigate thru all of them. This keeps the code scrolling to a minimum. and makes the App much easier to use and understand for the User and for the Coder.

If you go back and look at the "TDR DB Design.v.01.xls" upload, you can see a rough example of what I mean.

I have already started some of the generic Form and Database Utilities code.