My apologies...

Both the files are in the same directory: /home/manish/site/xsl

I am using name spaces. Before including the xsl file, I'm doing a
for-each at: WizardBluePrint/Property/Category/Group.In the included XSL
file I'm not doing any matches. 

The top of the master xsl file is:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:saxon="http://icl.com/saxon"
    extension-element-prefixes="saxon">

<xsl:output method="html" indent="yes"/>


The top of the included xsl file is :

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:saxon="http://icl.com/saxon"
    extension-element-prefixes="saxon">


The xsl:include is:   <xsl include href="textfield.xsl"/>

The XML is quite large. I'll include it if needed.

<Greg, I think you may have this already?>

I believe that's all of it. If there is anything else needed, please let
me know.

Manish

> 
>    You need to start giving more information in your initial posts, 
> Manish.  For example, we need to know where the two files are in your 
> directory structure (myfile.xsl and the current XSL Stylesheet 
> file).  Also, it would be helpful to know if you are using any namespaces 
> during the importation or matching that would cause the match to not 
> occur.  In addition to the relative file structure, show us the 
> <xsl:stylesheet ...> line of the imported file, the <xsl:import ... /> line 
> of the current XSL file, and the <xsl:template ...> line of the failing 
> match.  Not to mention the relevant section of the XML data file.
> 
> 
> Greg Faron
> Integre Technical Publishing Co.
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list