You could also (as a quick solution) just use the module locally. i.e. put the Net::FTP module in the local path and "use lib" to make the script find it... Net::FTP does not need much to work, and so can be fairly easily adapted to run as a local module I believe - As long as you dont mind the minor bloat in your code directory.

Course my "Reborn Perl Monk" side says, just switch ISP's to one that has common sense, and the idea that the customer should get what s/he wants.. but *grins at Kudra* there is still enough of the DarkSide left in me to say this:
In ASP, you can use the CDO (Collaberative Data Objects) to achieve what you are wanting - load the MSDN Library (if you have it - or go to MSDN Online - a free online version that is quite extensive and VERY helpfull) and look up how to use them.

Another - BETTER method might be to use WSC (windows scripting components - download the wizard doodad free) to make a COM controll out of Perl Script or compile a perl COM object with the ActiveState dev kit.. and use the ISP's precious ASP as the binding glue.

Keep in mind.. ASP will not do timed downloads for you, or any system event-trigering at all - like perl can. So, ASP will not solve your problems if you are wanting to do a timed daily transfer or somesuch, unless you manually go visit that page every day to trigger it.

Hey! Does anyone know latin for "Don't Let the Stormtroopers Get Ya Down?" *grin*

Update:Nolite te 'stormtroopers' carborundorum - Thanks Kudra

*G*