Kevin Burton wrote:
> Update. 
> 
> Again through trial and error I was able to determine that this "wrapper" in 
> the xsl seems to be  the culprit.
> 
> 		public bool MerchandisedProduct(string connectionString, XPathNavigator nav)
> 		{
> 		SqlFunctions mySqlFunctions = new SqlFunctions(connectionString, nav);
> 		return mySqlFunctions.MerchandisedProduct();
> 		}
> 
> It seems that if I use this wrapper with an XPathNavigator that points to 
> more than one node it fails. The reason that I know that it is the wrapper in 
> the XSL and not my function is that I changed the return so that it always 
> returned 'false' so the call was not made to my custom code.
> 
> Any idea on how I can change the wrapper so that it handles multiple nodes 
> as return by an XPath statement like:
> 
> bsi:MerchandisedProduct($CatalogConnectionString,Relationship/Relation/SKU)

Use XPathNodeIterator as the type of the second argument (and change the 
code of the extension function to make use of objects of that type 
obviously).

-- 

	Martin Honnen --- MVP XML
	http://JavaScript.FAQTs.com/