Either have 1 table per row, which means each row will display as it
loads, rather than waiting for the other 30 or so. Alternatively, you
could break it into chunks of 10, or 5 or whatever. I'm using both
these methods on a few sites, with no problems.
Justin French
--
PHP General Mailing Li
Maybe this is a solution for you:
instead of:
1data 1
2data 2
3data 3
4data 4
you can do this:
1data 1
2data 2
3data 3
4data 4
If you can't beat them, join them!
Greets,
Edward
"Adam Leckron" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> f
from the PHP manual
[flush()]
...Even the browser may buffer its input before displaying it. Netscape, for
example, buffers text until it receives an end-of-line or the beginning of a
tag, and it won't render tables until the tag of the outermost
table is seen...
even if you're flushing the buff
Good day,
As it has been said, this is a function of the browser.
You can get around this by not using a large table to render your data. You
could use one table per row, with all columns formatted with the same width.
You could also try to use containers to store the data, but in my
experienc
On Wednesday 30 January 2002 22:38, Bryan Gintz wrote:
> Hi.
> I have a large database query that returns anywhere from 10-30ish
> records. The problem comes from loading them in tables. With IE5 and
> Netscape 5 on windows, the results do not display until the last
> tag is written. Does anyo
Check the PHP manual on flush()
--Tony
On Wed, 2002-01-30 at 08:38, Bryan Gintz wrote:
> Hi.
> I have a large database query that returns anywhere from 10-30ish
> records. The problem comes from loading them in tables. With IE5 and
> Netscape 5 on windows, the results do not display until th
6 matches
Mail list logo
