Witango-Talk: Wierd

[Web Dude]

Witango 2000
NT 4.0
sp6a
IIS

I have a customer table that has around 1600 records. It has around 25 columns with various info (last name, address, ship address, phone, etc.).

When I build a search and search for all records, Witango bombs. It takes up 100% of the CPU and just spins. I have taken this exact same search and search a different customer table (Same columns different database) with only around 350 records, and it works fine. If I click off the get total rows it works fine, but of course I cannot scroll to next or previous pages. It is almost as if Witango can't take the return of all the rows in the list.

I have tried building a simple search with multiple page results searching for just the last name and I get the same result. Bomb City. Is it possible that the returning list is too large? And is there a place I can go to fix this?

First time I have ever encountered something like this. Could the Table be corrupt. Is there something in the config I need to adjust?

Thanks...
--
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body