Since you've found the FMS site, take a look through the articles. I don't have a link handy but Luke Chung wrote an excellent article a few years ago regarding the place of Access in the universe. He makes some excellent points about all the databases that are created and discarded either because they served their purpose or didn't do what was needed. Only a few ever actually make it to the attention of the all powerful IT department. Sadly IT looks at something useful created by a non-technical user and deems the product (Access) to be flawed and at fault because the techniques employed were technically unsound. They never understand that to get to this point in the life-cycle, this application has gotten very important to its owner and has risen up the ranks to being necessary to the corporation. When the department developed the app themselves, it was because the project was deemed unimportant and they couldn't get the necessary IT resources so they took matters into their own hands. IT should be looking at the app as a working prototype and thanking the developer for the requirements gathering effort. It is not productive for companies to forbid the use of Access. Doing that simply forces people into Excel which is an even worse tool for "database" development and shows a complete lack of understanding of how businesses evolve.
I have a very long professional IT background but I left corporate IT in the 90's because the inmates were running the asylum. I much prefer developing custom Access applications where I can actually produce meaningful products in a short time frame with a reasonable budget. I don't think I ever worked on a mainframe project that included fewer than 5 people and was scheduled for less than a year (I only did new development projects) and many of them could be recreated by a single Access developer in a couple of months. Once I discovered that Access could link to DB2 tables on our IBM mainframe and UPDATE them, I jumped ship at the earliest opportunity. Of course, most of my early clients didn't have multi-million dollar IBM mainframes so my early databases relied on Jet but nowadays, everyone supports at least SQL Server so I rarely use Jet and ACE any more except maybe as a jumping off point.
Regarding Total Access Analyzer - I use it on every new application I take over and periodically on my own during development but always at the end to create some documentation. This is not a tool you will use on a daily basis but it is invaluable in understanding an application created by a different developer. I find the cross reference reports especially useful.