I tried to make a case for replacing a background process we have to unload some data from a database, ftp/scp it, then load it to a remote database. It would be perfect in a dynamically typed language like perl, would not even require extra code to transfer extra sets of data, that could all be handled by a config file, or very little extra code. Its currently being done by an unreliable program in a nightmare of spaghetti code in a statically typed language. The decision was made that we're not going to use a non-MS solution, so we'll spend more time trying to fix the current process than to replace it all with perl. And eventually we'll replace it with VB.NET, because it's the latest, greatest buzzword. I am the only decent perl programmer in the shop, so it may or may not be a reasonable decision.