Replies to post #34502 on The Question and Answer Board (IHUB)

[Dimension]

ok..so the problem is the connection object, not the recordset object.

question/comment...from the code that you are about to put into production, how are you checking to see if the rs is a recordset and if it is open?

used to run into similar issues...the best way i have found to deal with this is to create a "wrapper" class for database communication. all queries pass thru this class, which is the only place where queries are executed, records open and closed. the data can be returned in a structure/call or even a disconnected recordset if need be.
that has helped greatly interms of reducing "orphan" connections and recordsets...

[Mattu]

Re: Site crashes and possible broken code

We are testing out quite a bit of new code tonight/Thursday morning.

If you get an error message of any kind tonight/Thursday, please let one of us know here, if you can post, or via e-mail at [e-mail] if you can't post.

As most know, we've been battling a bug that keeps causing the site to crash during peak hours, so we are trying a new approach to battling it.

To help debug things, send us the URL you were trying to go to and a copy of the page with the error message.

MB

Edit1: If anybody is feeling frosty, please, feel free to try out *everything* on the site. A couple of testers, myself, and Bob tried to find everything we could, but I'm sure we probably missed something.

Edit2: Most importantly -- I won't leave the ugly red error message up all day on Thursday, just for an hour or two into the trading day. :)