Search results for query: *

Well... I made the change to a disconnected recordset and there are no errors in the production environment yet today. This is a freaking miracle at the moment. About some of the other points made... GetRows and/or GetString, although used occassionally for some things, cannot work generally...

well, I don't have a conclusion just yet ... After I made the disconnected record set change you suggested, I logged into the app, ran the report and then simultaneously tried to update a record. No success. BUT, I could tell that others in the office COULD insert/update into the table while...

just had my first bit of progress in diagnosis in about a week ... be back with you soon... Tw3

This is actually the full function.... FUNCTION CmdExecute2(oCMD, IgnoreErrors) Dim Retries, DeadLock, NumErrors, ftr, HasErrors, ErrorDescription Dim RecordSetObject, DoRecordSetObject Dim objError, ErrorInfo Dim MailContent If LCASE(Left(oCMD.CommandText, 6)) = "select" and...

The confusion is around this point... the function is passed a command object that is developed elsewhere in the code. The function passed back the recordset. Actually, this function is a slightly stripped down version of the real one. I stripped out some of the logic that is used for...

also... changed the following lines of code: Set oCMD.ActiveConnection = Nothing Set oCMD = Nothing Set CmdExecute2 = RecordSetObject Set RecordSetObject = Nothing to... Set oCMD.ActiveConnection = Nothing Set oCMD = Nothing Set...

btw: even with the changes to help create this disconnected recordset, I still cannot get the darn thing to accept an insert/update while the recordset is being iterated through.

Regarding some of this... I am not certain I can recreate in QA. I will give this a concerted effort... I am pretty certain we are not hitting a connection limit. Connection timeout is set pretty low (30 seconds) and it never has a high number of concurrent users (probably max 80 serving a...

Our app is, under certain conditions, not allowing an insert or update on a table. We must fix this someway, somehow. Here is our scenario. BTW: We are using ASP Classic, ADO and SQL Server 1. We have a report query running. The recordset returned (in asp classic) in less than a second...