|laziness, impatience, and hubris|
The module you have problems with is really called "Config.pm" or is this just an example?
Just an example. It could be anything - Field.pm, etc.
Next question is ... is the working directory what you think it is? I believe some versions of IIS used to set the working directory to the web root, not to the directory containing the script!
We're running Apache on some unix-flavor.
In either case your modules should not be in the web accessible directories, it's better to have them outside the cgi-bin.
This is a fine workaround, I was hoping that there was something else - or at least a better understanding of why perl is even looking in these directories.
There are many popular packages that put perl modules in the cgi-bin. Moveable Type comes to mind.
In reply to Re^2: MS Frontpage, _vti_cnf directories and perllibs