Now that I know the exact term ( i read <!-- m --><a class="postlink" href="http://www.dpawson.co.uk/xsl/sect2/paging.html">http://www.dpawson.co.uk/xsl/sect2/paging.html</a><!-- m -->),I made some search about paging. They all talk about paging with XSLT onthe client side. What about the server side? I guess that will be a lot ofcharge for the server if it deals with the transformation, but my xml filesshouldn抰 be too big.He do have hundreds of users that will use my web app, so we can't ask themto install MSXSL3 for each machine, unregister the old DLL, register thenew one (as described in <!-- m --><a class="postlink" href="http://www.netcrucible.com/xslt/msxml-faq.htm#Q3">http://www.netcrucible.com/xslt/msxml-faq.htm#Q3</a><!-- m -->)...What do you think about this? Can it also be well done on server side?By the way, I抳e read a doc about a code-signed package that allows you toinstall MSXML3 to people's machines through their web browser but the userswill still have to remove the side-by-side mode (which means that installingthe MSXML 3.0 parser will not cause any previously installed version of theparser to be replaced). Does someone know something about automating thisstep and avoid users to manually replace the older parser with the newerone. (With xmlinst.exe installer tool I guess or is there other better tools?)Regards,Elise, XML learning girl 