# Attempt to lock only $data_dir/search.idx, if allowed
if ($file_locking ne "No")
{
        flock (SIDX, LOCK_SH) or die "Can't set lock for ".  
                "file: $data_dir/search.idx: $!";
}

# Read whole files in to arrays.  This is a really bad 
# thing to do if the files are potentially huge.  If 
# they are small (< 1000 lines), however this is okay.
my @sidx = <SIDX>;
my @sidx2 = <SIDX2>;

# Closing filehandles removes the locks
close (SIDX);
close (SIDX2);

# Make sure that the search files have the same lengths (I'm 
# guessing here, perhaps this isn't important to you).
unless(@sidx = @sidx2) {
        die "Search files are of differing lengths.";
}

# Remove empty strings from @skeyw and @premiumkeyw
@skeyw = grep {$_ ne ""} @skeyw;
@premiumkeyw = grep {$_ ne ""} @premiumkeyw;

# Build a big regular expression out of @skeyw and 
# @premiumkeyw for faster matching.
my $regexp = join('|', @skeyw, @premiumkeyw);
$regexp = qr/$regexp/;

foreach my $line (@sidx) {
        my $premiumline = unshift(@sidx2);  # destructive.

        # In the previous code you write:
        # $sline = $line, $premiumline;
        # this is the same as:
        # $sline = $line;
        # I'm going to guess that you mean the following:
        $sline = "$line, $premiumline";

        # Do our test to see if this matches our regexp
        if($sline =~ /$regexp/) {
               
                # do something with search results

                $resultline[$icnt] = $line;
                $icnt++;
        }
}
[download]

Hope this helps

jarich

Update: Fixed rather embarrassingly wrong use of != instead of ne in grep.

Also changed pop to unshift so elements come through in the same order.

Thank you for your response jarich. I tried your suggestion and now neither side would populate the flat file results are returned. However, I do feel more comfortable with the way you rewrote it because it is easier to handle. To truly understand my dilemma, I have included the following link. The HTML file before it is populated: http://www.urhosted.com/mall/searchres.html By doing a search for "sports" at the bottom of the HTML doc, you will see only the %%searcresults%% side is populated with the results from search.idx file. Example:

    20645    CJ Sports    Sportswear and equipment retailer specialisi
+ng in rugby, hockey, netball and cricket.  Full product details and o
+rdering available online.                Apparel_and_Accessories-Athl
+etic_Clothing    www.cj-sports.co.uk/
        
    20660    Gekko Gear    Selection of winter sports apparel.        
+        Apparel_and_Accessories-Athletic_Clothing    www.gekkogear.co
+m/
[download]

The data in the second file - search2.idx

    20225    URHosted    Testing.  Testing more.     Apparel_and_Acces
+sories-Athletic_Clothing    www.urhosted.com
[download]

Thanks for code. I just needed to add a right bracket. However, the 2 arrays populate both includes showing the same search results. I there any way to adjust this? I like the way the arrays pull in the filehandlers so I'm hoping that does not have to be adjusted.

To be honest, I'm not quite sure what you're asking here. So I'm going to take a wild stab in the dark. You say the 2 arrays populate both includes showing the same search results.. I'm not sure what you mean by both includes and I don't know if you've added any code to the section where I wrote do something with search results.

If you have, you should show me the relevant code.

What the code I've provided you with does is the following. For each element in @sidx, copy that element into $line and REMOVE an element from @sidx2 which is put into $premiumline. Note that this means that @sidx2 will be EMPTY at the end of the foreach loop. (To avoid this make a copy of @sidx2 before the foreach loop and unshift off that instead.)

Once we've got $line and $premiumline we join them together into $sline. We then test if $sline matches what we're looking for in either $line or $premiumline and if it does we SAVE (only) $line into $resultline ($premiumline then gets thrown away).

Maybe this isn't what you want to be doing. Maybe you want to be doing this:

• Foreach element in @sidx, keep it (save it in @resultline) if it matches any test in @skeyw.
• Foreach element in @sidx2, keep it (save it in @resultline2) if it matches any test in @premiumkeyw.

Maybe you're trying to do something else...

Since you haven't specified what you want to be doing I think it would be futile for me to guess. Think about what you want to do in a broader sense and I'll be able to help you better.

All the best,

jarich