Hi,

Yes it's javascript on the client that runs from the HTML BODY onload event.

The xsl transformation happens on the client I believe, as the server just 
sends xml with the xml-stylesheet defined.

We are using MSXML4.

Basically, an ASP Page on the server retrieves the data, and writes it to 
the response object. 

When the HTML is written on the client by the xsl stylesheet, I guess the 
event for onload is fired and runs the procedure that positions the data 
elements where they need to be.

It's all dynamic, so the same xsl page and asp page can query multiple on 
multiple databases on multiple servers without modification, using a generic 
display...

now normally it all works great, does the job perfectly, but I really want 
to seperate some of the code out if possible for maintenance reaons.

thanks

Philip
"Martin Honnen" wrote:

> 
> 
> Philip wrote:
> 
> 
> > we have a very complex xsl stylesheet of 1200 lines or more and it seems 
> > like a good idea to seperate parts out into different xsl sheets that can be 
> > imported.
> > 
> > The problem is that in the BODY onload event we run a procedure that moves 
> > data fields into their correct places ... and after we move one of the larger 
> > sections of xsl into a seperate sheet, it fails. The section that we want to 
> > move in fact creates the data fields based on metadata in the xml file.
> 
> BODY onload sounds like script (usually JavaScript, with IE/Win VBscript 
> is also possible) in a HTML document. Such a HTML document might be the 
> result of an XSLT transformation but I wonder how that relates to 
> using/importing stylesheet modules or not. Can you provide some more 
> details? Where does the XSLT transformation happen, on the server, or on 
> the client? Which XSLT processor do you use?
> With the failure, do you get any error message?
> 
> 
> 
> -- 
> 
> 	Martin Honnen --- MVP XML
> 	http://JavaScript.FAQTs.com/
>