You probably don't even need the script section in the XSLT to do the 
processing, unless you're trying to do something not easily done in 
XSLT--like regular expressions, or date calculations, etc.  

I just heard from a client of mine, and he wants my updated application (the 
one I mentioned), so I'll probably be finding time to work out a better 
example of dynamic filtering and sorting, but you can take a look at this one 
in the meantime:

http://rdcpro.com/Members/rdcpro/snippets/filterandsort/

This isn't the best way, if the document is large, but it will give you an 
idea.  

I've got some improvements on it, and if you send me an email, I'll send 
some more stuff for you to look at, in particular another XSLT that filters a 
large document (a couple thousand rows, about 2MB) using wildcard searches, 
and other stuff.  When I get the final version with the dynamic search 
parameter parser finished, I'll post an update to my web site example.


Regards,
Mike Sharp

rdcpro@h...


"Greg Collins [InfoPath MVP]" wrote:

> I'd be interested in seeing an example. The one issue I have (which I think can also be done with an XSLT file) is that before I process items 1-6, I do the following:
> 
> Working with a cloned copy of the DOM, I strip out large sections I don't want to deal with.
> 
> Then there are a whole series of items which are conditional -- the problem is the conditons must be figured out dynamically... so grab all of those items with conditions, test the condition in code, and remove the item and its children if the condition fails, as these items must not be part of the results.
> 
> Then I'm left with a much smaller subset which I process #1-6 on.
> 
> I believe I should be able to add a script section to the XSLT file to work in as part of the processing.
> 
> What do you think? ... Sorry I have to be so vague about everything... business work and all :)
> 
> -- 
> Greg Collins [InfoPath MVP]
> Please visit: http://www.InfoPathDev.com
>