Have Geek Brain

ADO SQLServer dbGo generates EAccessViolation

I have a program that populates a DB in one thread. I am using one connection for all requests. This is how I can run them all in transactions.

Every second I get a new set of files to be injected into SQL Server 2005 Express.

The app can run for 24 to 36 hours and then suddenly get "EAccessViolation" in the request.

This request had by then been executed at least 24 * 60 * 60 times.

I'm not sure if this also happens with requests without parameters, because most requests (90%) have parameters. they are inserts / updates or are selected with parameter (s).

when this happens, all requests then get the same EAccessViolation, and after a while I get StackOverflow.

As long as the code is designed in sutch so that the exception will be handled and next time the code should work without problems.

the fact that this happens in varios queries (which have not changed from the previous version) with the only change being that instead of using dbGo from BCB Builder 2007 we did ADO with Cpp Builder 6.0.

I'm guessing it's a bit in the Windows version of MDAC (2.8) or in dbGo from CodeGear. The fact that in the previous version (ADO BCB6.0) we did not encounter it, and now with (dbGO and BCB2007), we do it very suspiciously.

I hope some have good ideas on what might be causing all this.

At the moment I cannot reproduce it here on the desktop. I am still trying to reproduce it, which will give more details.

I am open to suggestions.

considers

jvdn.

0


a source to share


1 answer


I would suspect a driver - try using a different one to see if the problem can be isolated. Also try rewriting the query to use a different syntax, perhaps you could rebuild the connections that often?



0


a source






More articles:


All Articles