Thank you for your response. I think I was looking at the tool correctly then and I don't think it can help me effectively. My collection could grow to many thousands of records over time and I only needed to print out maybe 30 of them. I needed to get to the starting record and to the final record. I could have placed the object in a "special" class to do this, but no option was very clean.
The problem with handling it in velocity is that the template would still be processed because there is no "mill.continue()" method that would stop the parsing till the #end of the foreach loop. Yes you can avoid the printing with "if" statements but you still have tons of overhead in very large collections. In the end I did it the long term correct way. I did the wise, extra programming that would only return the 30 records I require to the request. I only respond back to show the problem I was facing of trying to avoid having to repeatedly process large sections of template code when faced with large collections. ...and as usual much thanks. The latest Velocity is working very well in production under pretty high load. I am using it on about sixty forms. JohnE --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
