Hello Todd,

I've been using Foxweb to deal with very large sets of data and it's quite fast; however, my server is a Pentium II, 450 MHZ with 356 K ram (which I consider low end). But this is for development only; in the real world I would want to use a top of the line 1000 MHZ, 1000 K RAM late Pentium model.

You also have to consider the memory of the workstation that is browsing the data. When I am displaying a very large table, I have noticed that even though it takes Foxweb a few split seconds to process the data, it can take the browser up to a minute to process all the html code that makes up this table, if the table is very long.

For this reason I have set up a paging routine that allows users to set the number of lines of the table they want to see; users with low end computers can choose under 10 lines; users with higher end computers, 100s.

That 96 K level of memory is extremely small. When a program runs out of memory it has to make room for more memory by writing packets of data from RAM to hard disk before it can process more data. Then it has to do the whole thing in reverse. If you have very limited memory; it may have to iterate through this routine over and over to process just a little data. If you hear your computer's hard disk whirring and cranking back and forth when you browse the page, this is probably what is happening.

I would try to expand your RAM.

When writing programs for the web, it is more efficient to let Foxpro do most of the work, because of its extremely fast database engine, and take the load of the browser, which is much slower. A way to save time might be to write a SQL, or create a cursor that incorporated the text that you are creating with your code, rather than making the browser do most of the work. But with limited memory, your browser will have a hard time processing any sort of very long web page.