Maximum Search Results?

[Unamailer]

Hello, everyone. I am having trouble with a query that I am performing.

I have a database with a measly 739 records. If I try to perform a search of
all records in the DB, it returns the page with my heading of "Displaying
records 1 to 25 of 727". It starts listing my column headers and craps out at
various points throughout the code. These points are different every time I
submit the query...one time, it may crap out after the <A of a link tag...the
next it may crap out before it even gets to that link tag.

It seems that it isn't processing the code or something. One time it
displayed my code on the page, as <IMG name="desc" alt=="sort in descending
order">. It didn't render the code or anything. It just displayed it as if I
had typed it in text or something.

After that, it won't even recognize my cookies that I have coded. I even have
them CFPARAMed, so that they will at least be defined if something freaky
happens.

Is there a maximum number of records that I can retrieve? This worked a week
ago when I tried it and the DB had less records.

Please help! I am stuck until I get past this issue, and it is holding up a
production due date.......

Thanks for any help that can be provided.

[mpwoodward *TMM*]

On 2005-05-16 13:59:16 -0500, "Unamailer" <webforumsuser@macromedia.com> said:

> Is there a maximum number of records that I can retrieve? This worked
> a week ago when I tried it and the DB had less records.

What database are you using? There's no maximum number of results in
theory, and the number you're discussing shouldn't really be an
issue--I have an app returning 800-900 records for some "wide-open"
searches that does just fine.

I'd be curious to hear what database you're using or get more
information about your setup. I do remember when I was using Access on
a Java application several years ago (don't ask!) that I had to put
some threads to sleep momentarily to allow Access to catch up, but if
you're using a "real" RDBMS like SQL Server, MySQL, Oracle, DB2, etc.
returning 700+ records wouldn't even make the database blink. Dealing
with them on the web app side *might* be an issue if you're on an
underpowered/overutilized server but let us know more about your setup
and post the relevant code so we can better see what's up.

Matt

--
Matt Woodward
[email]mpwoodward@gmail.com[/email]
Team Macromedia - ColdFusion

[Unamailer]

Matt:

Thanks for the reply. I am using a MS Access database (can't get the company
to buy a copy of SQL yet).

However, I actually found out what my problem was. Here goes:

When performing the query, I am pulling program number, program date, and
error code. Each program number is 8 characters in length. Once the query is
performed I am creating an array to store the program number associated with
each record. I then store that array as a list (using ArrayToList) into a
cookie.

Problem is, when there are a little more than 450 records, I am storing more
than the cookie can hold. They have a max length of 4096 records (4KB). I
wasn't aware of that length size limit of cookies. So, needless to say, 738
records were blowing that limit to pieces (more than 6500 characters, including
the delimiter in the list), causing the code to crap out.

Again, I appreciate you taking the time to look into it and reply. Also,
sorry to waste your time with my ignorance! :o

Have a great week!:beer;