Hello Again,

Well it certainly sounds as if you have taken on quite a task, but one which I am confident that you'll be able to manage from the sounds of things. Perl, while quite large architecturally, is easier to learn because it is intuitive; much more so than C(++), so you'll quickly be able to comprehend its intricacies.

OK, after that ego booster, let me say that I would IMO move to a *nix based box for development. Apache/unix are what Perl was originally intended for, and sits quite at home in this platform. If moving to linux is out of the question, you might find it easier (and more secure, etc, etc...) to get the win32 version of Apache, to replace crusty IIS.

If MYSQL is bogging you down (I'm so impressed with MYSQL, but it is quite bloated and generally best suited for applications where numerous simulatenous queries are performed), you might consider reimplementing the built in functionality of Berkely DBASE access in Perl (not sure how this works on a win32 box, if at all). If you have the Llama, Berkely DBASE is covered in one of the last chapters, and in only a few pages can get you on your feet using this aspect. I use Berkely almost exclusively, because my databases are generally large, but not accessed simultaneously. Also, I don't really need all the inherent permission capabilities, etc, that MYSQL has.

I think everyone has difficulties now and again installing modules from CPAN; with such a disparate number of extension Perl can take on, it's easy to find yourself in dependency hell. I would recommend <plug> installing Slackware Linux </plug> and building Perl from source. Maybe even create to parallel installs, one for mucking about with new/untested modules, and a stable/quasi-vanilla one that you can use for important/main development. That's what I do at least.

That's long and my thoughts are rambling, but I hope it gets you on track.

------------------------------------
"There is more in heaven and earth
than is dreamt of in your philosophy"