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 :)

--=20
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



"rdcpro" <rdcpro@c...> wrote in message =
news:A10D8455-2645-47C2-9218-618B7531BA69@m......
Then I would definitely use XSLT.  DOM methods in javascript, especially =
with=20
large documents, are pretty slow, but MSXML 5 runs them pretty quickly =
in an=20
XSLT.

If you use the XSLTemplate Processor, you can set parameters, and direct =
the=20
result of the transformation to a DomDocument object, that you can=20
subsequently use in your InfoPath form. =20

I have a variety of examples of using javascript and the XSLT Template=20
processor, if you need an example.  I was going to add a new dynamic =
filter=20
and sort example to my website that uses the faster approaches that I=20
mentioned, but haven't gotten around to it yet.  I haven't tried using =
the=20
XSLT from within an InfoPath document yet, but I've used DOM methods to=20
update the data source in an InfoPath form as you've done, and I don't =
see=20
why it couldn't be done with XSLT. =20

Regards,
Mike Sharp

http://rdcpro.com

"Greg Collins [InfoPath MVP]" wrote:

> I didn't get to read your whole response as I have to take off for the =
day, but to answer your last question: this is JavaScript in InfoPath.
>=20
> --=20
> Greg Collins [InfoPath MVP]
> Please visit: http://www.InfoPathDev.com
>=20
>