I'll bet your supervision is more interested in you maintaining/fixing/embellishing the current db as opposed to you making yourself into the new Access guru. With that in mind, my recommendation would be to print out the existing code (which probably wasn't sufficiently commented so that you could grasp the intent of it) and sit down to read it. Armed with pen, write every question you have about the code, near that code, then explore (Google) your questions. There are TONS of videos and websites out there, which might be more conducive to what I think is your immediate task, since you will be able to focus your research on aspects of your current db. Once management sees you're able to at least provided the necessary coverage to the current db, they should be more receptive to you taking outside courses if that's your wish (which they should pay for). Likely, their issue would be that to make you into the next guru is only good for as long as you remain employed there, a fear which doesn't usually bolster your request.
While you're learning how to maintain your db, watch for variations on how basic things are done (such as naming things) and add to your question list as you go. I'd advise you to take the approach that your goal is to achieve a level of proficiency that allows maintenance and improvement of the current db, and to be able to suggest new applications to make business processes or decision making more effective after you've learned why things are done a certain way, not just how.
Access has a database documenter you might want to look at, but I don't think it allows you to print out code. Best advice I can give right now is to play with copies of the database BUT you must understand the way a be and fe is linked. If you copy both to your personal drive and play with the data, guess which one you modify - the main application/production one. In your copies, you must break the be links and relink your copy fe to your copy be.
BTW, without knowing anything of the business process for the db, it may not be fair to say that the number of queries, forms and reports makes me think that there might be some unnecessary duplication of these objects. If for example, if 2 reports are quite similar in appearance, but are based on different departments, it's likely they don't both need to exist.
Last edited by Micron; 01-17-2018 at 12:23 PM.
Reason: spelin and gramur
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.