The script didn't work before the installation but it was just saying syntax error. This is my first attempt at perlscript rather than perl, and I was hoping win32::asp would be gentler on me

the script looks like this btw (it's building a decent query string for a site search.)

use WIN32::ASP;

$sqlStatement = "";

If (GetFormValue('SearchText') ne "")
{ 
    my $conj;
    my $query=GetFormValue('SearchText');

    $query=~s/([\(\)])/ $1 /g;
    $query=~tr/A-Z/a-z/;
    $query=~tr/a-z0-9() //cd;
    $query=~tr/ / /s;
    $query=~s/^ //;
    $query=~s/ $//;
    
    foreach $word (split(/ /,$query))
    {
        if ($word=~/^(and|or|not|\(|\))$/)
        {
            $word=~tr/a-z/A-Z/;
            $sqlStatement.=" AND" if (($word eq "NOT") && ($preWord!=~
+/^and|or$/i));
            $sqlStatement.=" $word";
            $conj=$word;
        }
        else
        {
            $sqlStatement.=" AND" unless ($conj || !$sqlStatement);
            $sqlStatement.=" keywords LIKE '%$word%'";
            $conj="";
        }
        
        $prevWord=$word;
    }
}

$sqlStatement="WHERE $sqlStatement" if $sqlStatement;

$Response->Redirect("search2.asp?searchtext=$sqlStatement");

%>
[download]

checking control panel shows me I do indeed still have activeperl 522 installed in addition to build 805. Trying to remove it causes an illegal operation as well. I'm now removing 805 in the hope I can then remove 522, and start over.

If that fails you can double check your path environment variable to see if you can convince it to use the correct version of Perl.

I'm not familiar with Win32::ASP, so can't comment on that at all. But what was the syntax error you were getting prior to this?

it appeared to be complaining about the ;

my $conj;
my $query=$Request->Querystring("searchtext");
[download]

returned syntax error near "; my"

anyway I've stripped all versions of perl off, and reinstalled 522, and it's now all working fine.

Well I say fine, but I hit a far more amusing problem. I was building a sql search string and passing it in the querystring to an existing asp script. Unfortunately the "keywords LIKE '%project%'" was, quite sensibly, seeing "%pr" and decoding it. It gave me quite a start when SQL threw back errors full of wingdings :)