I'm having trouble with an ASP/VBScript driven application. For some reason, when I connect to an Oracle 8.1.6 Database and Execute an SQL Query...the results are very erroneous.
I have two applications:
Application A, which is erroneous on SQL queries
Application B, which ALWAYS works and returns the proper rows.
Sometimes Application A returns the desired rows. Other times, it returns nothing and I get an EOF for the first Recordset read.(even though I know there are rows there...identical query to the first one).
One way I've found to "refresh" the application is to STOP/START the IIS Admin Service and But, this gets pretty tedious.
Another way I've noticed is with Application B, I can try to query the same Database (and it works all the time with App B), then if I go an try Application A again...it works sometimes (other times it doesn't).
There are multiple users using these apps at any given time.
I have played around with everything in terms of ADO Objects, Opening, Closing, Set to nothing, etc...but I don't see anything different between the two in terms of database connectivity or management.
Any ideas what could possibly be causing App A to sometimes return an Empty Recordset?
i.e.
Not closing the previous connection properly?
Resource (ASP.DLL) contention with multiple users utilizing the same app?
Any suggestions on how to catch any potential errors?
Any assistance would be greatly appreciated...Thanks!
I have two applications:
Application A, which is erroneous on SQL queries
Application B, which ALWAYS works and returns the proper rows.
Sometimes Application A returns the desired rows. Other times, it returns nothing and I get an EOF for the first Recordset read.(even though I know there are rows there...identical query to the first one).
One way I've found to "refresh" the application is to STOP/START the IIS Admin Service and But, this gets pretty tedious.
Another way I've noticed is with Application B, I can try to query the same Database (and it works all the time with App B), then if I go an try Application A again...it works sometimes (other times it doesn't).
There are multiple users using these apps at any given time.
I have played around with everything in terms of ADO Objects, Opening, Closing, Set to nothing, etc...but I don't see anything different between the two in terms of database connectivity or management.
Any ideas what could possibly be causing App A to sometimes return an Empty Recordset?
i.e.
Not closing the previous connection properly?
Resource (ASP.DLL) contention with multiple users utilizing the same app?
Any suggestions on how to catch any potential errors?
Any assistance would be greatly appreciated...Thanks!