I think I agree with all of the responses here.  However, let me offer a different angle for you to consider:

What do you want to do?

Your posting has a comment in the signature section that reads, "I am a true geek".  If that's so, why would want to do this project in Access, considering the limitations and lack of lustre?  I would imagine that you registered for the Perl Monks site because you're attracted to Perl.  If you want to learn Perl and you're going to be the one solving this problem at work, and it's your decision, why not use this project as an opportunity to learn Perl?  Of course, if you have a tight dead-line and are comfortable putting the whole thing together in Access with a bunch of macros, well alright.  But if you want to have fun and learn Perl, then do it in Perl.

Another angle to consider, one that is less psychological, is what are your long-term data goals for this company?  Is this project going to be a small one and the only one?  Or is this a project that will be extensive over time and will need to tie into many other data manipulation related projects that you envision?  Basically, don't create something that you'll end up replacing later and learn nothing from now.

I'm an IS manager for an office of about 250 employees and four locations.  My vision for our data needs and requirements include inter-networkability and intertwining of all data through an intranet site.  Also, I require stability so that the users can depend upon the system and so that my tech. support is minimal.  I also need easy accessability through the internet in a text based, command mode--I carry a Handspring Visor with a modem to do tech. support when traveling.  These requirements are easily satisfied with a web-based front-end, using Perl for CGI and especially for many behind the scenes processes initiated daily by cron.  I've also filled my requirements with the mySQL database and Linux servers.  The result has been stability all around, easy to learn interfaces, and easy to access data from anywhere we have or open a branch office or whereever a traveling salesman might go.  It also has resulted in minimal maintenance work on my part and I don't have to leave my house (or hotel when I'm traveling) to fix things.

Okay, that's my old man and pop-psychology advice for the day.  I hope it was helpful.  Good luck.