GetRows

[AndyApp]

Is there a limit to the amount of data that GetRows will bring back? I've two versions of my site and two sets of data. The development version works perfectly but the live one is falling over at the getrows statement.

When I changed the development site to look at the live data it too fell over at the same point. It's bringing back approx. 300,000 records! Is it just too much? It doesn't time out, it just doesn't do anything. Could there be something in the live data stopping GetRows from working?

 

[AndyApp]

The search is working ok for searches that bring back less results. however, when i took GetRows out and just printed the ID straight from recordset it fell over as well. i.e. instead of GetRows i just did response.write(ors.fields("id")). This worked for the smaller search but still failed for the larger search.

Now i'm really confused.

 

[DotNetGnat]

300,000 records is a lot of records for displaying purposes...

why dont you consider paginating your recordset besides using getrows method for efficient results...

-DNG

 

[AndyApp]

yeah it's a bit awkward but I am paginating the results. It doesn't display all 300,000 as a lot are duplicates. I loop through them and just display each record once.

 

[johnwm]

Could you tidy up your query using Distinct keyword to remove dupes first? Or could you pre-qualify the query , maybe by initial letter, or by month or year or whatever suits your data?

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller

 

[AndyApp]

I managed to solve it. I was being a fool! I didn't need to inner join so many tables that were causing the duplicates for this particular search. doh!
thanks for the help