David,

Yeah there was a quotes based error in the script code that I was able to find once I got the script debugger to run. During most of the testing I was using just a static test value not the parameter. The working code is now:

if ( cFilter > '' )
   filterBy.value = 'VFPData/dbservers[contains( servname, \'' + cFilter + '\' )]';
else
   filterBy.value = 'VFPData/dbservers';

The unknown method name error was coming from a namespace problem. So now my declaration is:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
   xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
   xmlns:msxml="urn:schemas-microsoft-com:xslt" version="1.0">

But this breaks the sorting code that I had because the order-by phrase I was using now throws errors. So today's quest is to get both qorking at the same time.

>Instead of referencing the cFilter JavaScript var in the filter expression, how about building up the filter expression with concatenation, inserting the value of cFilter into the string between quotes? (I don't know if it has to be single or double quotes around the value, so you might have to do some fancy footwork.
>
>IOW, does this work?

filterBy.value = "VFPData/dbservers[contains( servname, 'PROD')]";

If so, maybe the problem is that the JavaScript var is out of scope and can't be seen in the XSL transform.... Just thinking out loud...