How much experience do you have with MS Access? While the details can be very different, the essential design process can be much the same.
Analyze your user's needs and current procedures (Sounds like you've at least started on this)
Then you usually create at least an initial design of your tables and their relationships.
Then you outline the data entry tasks and reports in a general way (avoid getting bogged down in details).
Then you cycle back through your table design to see if you have the tables and relationships you need to support the layouts you just created.
Once you've got a basic outline down, you can work out the details layout by layout (That's where value lists and many other features come in.)
You also need to check back periodically with your users, presenting prototypes of your layouts for data entry and reports--often such examples trigger responses like "that's not quite what we need" or "Oh, I didn't know you could do that! Can we also do this..."
It's never been a straight line process for me. You often find you have to loop back through your table and relationship design to consider changes driven by an improved understanding of what final results are needed.
For additional training, there are certainly training tutorials and books you can purchase.
I am the end user, so I know what we need and I can visualize it. It is just knowing how this all works. I would say my experience with Access was as a user and creating queries, that was about it. You plan makes sense, at least I know I am on the right track.
Thanks for your input, greatly appreciated.
There is a formal technique (Entity Relationship Modeling) that can help you document and evaluate your requirements as you proceed. For small data models, it is probably overkill. But for someone starting out, it will provide a visual clarity to your design.