The Question and Answer Board

[BullNBear52]

I don't know if this logic works...

From your earlier post.

Each one was a complaint that a recordset.close was being attempted on a recordset that didn't exist. Hmmmm... In each of those ASP's, the recordsets weren't being explicitly closed anywhere prior to the line that was erroring out, however, something they all had in common was that the recordset.close was being attempted *after* the subroutine that does all the end-of-page processing.

And this post.

"If everything is the same except that the machine it's running on is much more powerful (and has twice the memory), why the problems?"

Could it be that the old webserver do to it's slowness allowed for the recordsets to close. And now that you're running on a faster machine the processor is getting ahead of itself do to a software related issue. (Not neccesarily a code issue.) Then the processor in effect loses it's place?

In other words, I can onlt execute one thing at a time and the software is too damn slow and not keeping up?

Do you follow?