And in response to merlyn's question, I've run into scenario's where my end-user is skittish about installing a Perl distribution on their system (and I'm skittish about learning VB). So as a solution I commonly use PerlApp or PerlCtrl to create stand-alone .exe's or .dll's that I can provide to them.

-Nitrox

I blame my spastic fingers for that one. I thought I typed a 1 but apparently I didn't. My "ouch" still stands, however - I can't justify spending that on development tools that I may or may end up using heavily because programming is something I do mostly for my own entertainment at this point.

I will look into this as I am using Windows(NT,2000,XP), Linux, Solaris, HP-UX, AIX, and Netware. The more platforms it supports..the better.
-P0w3rK!d

-P0w3rK!d
P.S. Don't tell merlyn you're using a Perl compiler or he may send the UN Inspection team after you! lol

My client requested it :/ They were afraid the script would get served to the users of the system accidentally.

Update: If you downvote my nodes, please tell me why. I don't know what you found wrong with this node and if you don't tell me, I can't avoid doing the same thing in future.

I know, and most Perl people know, that the source never leaves the server unless it's horribly misconfigured but they were insistant that this was the way they wanted it. You don't argue with a client like that. I explained to them why it wouldn't be served to the users but that was not enough to convince them. It's not like I didn't give them the source; They wanted a binary as well.