I think you missed my point which is: do you want workstation software running on a server? I then gave an example of where parts of Microsoft Office (a workstation product of which Access and Outlook are both parts of) cannot co-exist with a Microsoft server product. Forgive me for trying to point out potential risks you may not have been aware of.

I understand how Access works which is why I recommend against it. We used to have an Access frontend to Oracle here. We ran into a serious performance issue where ODBC would not take advantage of indexes. And every time updates to Access were rolled out it could break the front-end (and usually did). And upgrading to a new version of Office always broke the Access frontend. I'm sorry, but if you think Access is a good idea you just do not have enough experience.

Regarding IIS, ActivePerl ships with Perl for ISAPI so you may still be able to use Perl.