As am I As you can see from the code example I posted earlier, the HTML table is broken down into sub-tables which render very quickly (at least under Netscape) compared to a huge table with the same data. The code was: <dtml-var standard_html_header> <dtml-var "ZopeTime()"> <dtml-call "REQUEST.set('count', 0)"> <TABLE> <dtml-in allorders> <dtml-call "REQUEST.set('count', count+1)"> <dtml-if "count>100"> </TABLE><TABLE> <dtml-call "REQUEST.set('count', 0)"> </dtml-if> <TR><TD><dtml-var itemno></TD><TD><dtml-var desc></TD><TD><dtml-var datelastmn></TD></TR> </dtml-in> </TABLE> <dtml-var "ZopeTime()"> <dtml-var standard_html_footer>

...

---------- From: Bill Anderson[SMTP:BILL@LIBC.ORG] Sent: Thursday, March 22, 2001 9:15:06 PM To: Capesius," Alan Cc: zope@zope.org Subject: RE: How slow should dtml-var be? (was: RE: [Zope] Problems with * BIG* SQL queries) Auto forwarded by a Rule

On 21 Mar 2001 13:18:38 -0600, Capesius, Alan wrote:

...

Let's clarify that here...large tables not lots of tables. As I showed in my earlier messages in the *BIG* thread, a large table (31000 records) may take 15 minutes+ to render whereas the same data parsed into 300 tables renders very quickly (seconds).

i believe Andy is referring to _HTML_ tables, not SQL tables ...

...

...

...

...

rendered, for example lots of tables on Netscape. Your example includes no HTML so thats just an off the wall comment.

Bill