Desktop VS network VS Web
All users have access to central network server in a shared directory environment. I should be able to deploy the app via a single batch file without any desktop issues. I'm pretty sure I don't even need to install Perl, just set the environmental variables correctly. There will be no monthly desktop issues at all. A single control file that is modified on the network is all it should take for any changes.
I really dislike the multi-level dependancies of web apps. 1st I have the issue of language. If I use Coldfusion (which is our default corporate web environment), I am immediately out of my league. Remember, I need to write an interpretive engine as well as a presentation interface. I can do this in a day or 2 using Perl. It might take weeks to months in CF for me, and our CF programmers do NOT have the Little Language mind set, which would mean CF programming for every change. Or I bully my way into non-standard, use PHP or Perl back-end, but then need to deal with the IT group and web server issues, which is to be avoided if possible.
I also HATE the interactive feel of web apps, A personal issue, but I will avoid using an environment that I can't truly control the layout unless I need out of house deployment. This app is for our internal MF programmers. It will never be used by a customer.
So, control, limited internal politics, expertise in the language, no overriding need to go into a complex web framework, (I'm sure I can come up with a bunch more now that I am in rationalization mode) lead me to a real desktop app. I don't see a downside to it, while web crap (I HATE IE SUPPORT) has always caused me pain.