[thelist] Re: Bad DB Data?

Adam Slesinger badlanners at hotmail.com
Tue Dec 3 09:14:01 CST 2002

Thanks for the clarification, rudy.  Of course, you were right.  Turns out I
wasn't indexing properly.  I couldn't tell you why the script would timeout
when going through a certain block of records, but with the recordset
sorted, there are no more timeouts.  I had orginally thought bad data was
the continuing culprit because quotes and semi-quotes in the field names
were the first thing causing it to break.  Thank you much.


> i'm sorry, perhaps one has to be biased, like me, but the problem you
> describe is likely how your code is handling the data, rather than the
> itself
> infinite loops fall in this category, although i am not suggesting that's
> what's causing your problem
> if the problem is repeatable on a certain few records, you will no doubt
> soon find them
> these records may indeed have what we would call bad data, even after you
> have cleansed them of "backslashes, forwardslashes, quotes, and
> when you find the culprit records, i'll have a look at your select and
> update queries if you like, although i won't be able to help with your asp
> code

More information about the thelist mailing list