Unfortunately, many corporate IT departments have no-Access policies. This is a shame, because when you take Microsoft Access out of the equation you leave a gaping hole between overtaxed Excel workbooks and wildly expensive custom enterprise applications.
Don't Let the Perfect Be the Enemy of the Good
Many software developers scoff at the idea of building anything in Microsoft Access. "If you're going to do a software project," they say, "you may as well do it right."
But this assumes that there's a budget to do a traditional software project and that management is just "cheaping out" by going with Access. Here's the thing, though. The choice is almost never, "Should we do this in Access or should we do it as a 'proper' software project?"
Rather, the choice is often, "Should we do this in Access or leave it in Excel?" And if you've gotten to the point where you're asking that question, there's really only one answer.