AV in IDAPI32.DLL

[John Faris]

Hi all,

I have posted this a couple of times before in the past and never got
anywhere but here goes again just in case. Every now and again one of the
users of my app gets the following error:-

Access violation at address 4BE34602 in module 'IDAPI32.DLL'. Read of
address FFFFFFFF

It happens either on a TStoredProc.Open statement, a TStoredProc.Close
statement or a TQuery.Open statement. In the last year it has happened
maybe 20 times. On one occassion I got a slight variation as follows:-

Access violation at address 4BE34602 in module 'IDAPI32.DLL'. Write of
address 0022012A

I cannot believe that thsi has not happened to anyone else due to the wide
variety of client setups it has occurred on e.g. 95, 98 and NT. Also the
tools I am using are so widespread that surely this has been seen before. I
read somewhere that AVs like this could be caused by BDE timeouts going
belly up, but have not been able to substanciate this. Can anyone help at
all, please?????

John.

--
I am using Delphi 5.01 Enterprise
with BDE 5.11 and MS SQL Server 6.5

[Dave Gray]

Hi John,

This look very similar to a problem we are experiencing with D5 & SQLSvr7
connected via ODBC, when we Close queries or procs we intermittently get AVs
in IDAPI32.dll, I have also seen errors at the same point from IDODBC32.dll
and don't know if these are related !!

We have reviewed the code and cannot find a cause, stepping through fails to
reveal anything except a fatal exception as we close the query. All I get
looking from SQLServer profiler is a Disconnect. We wondered if we were
hitting a max connections or some similar limit but, so far we have no
resolution.

We have also experienced the application exiting on these AVs with no
messages being raised at all, just 'click and it's gone'.

If anyone has similar problems or any clues about where we should look for
answers I'd also be happy to read about them.

Dave.

"John Faris" <john...@tsigroup.co.uk> wrote in message
news:8vj4gd$13...@bornews.inprise.com...

[Jonathan Dearson]

I have had this one as well, and I'm using MS Access 2000 through the ODBC
and C Builder 4.
I and I'm afraid I haven't found a solution to although it usually happens
after something else has gone wrong.

[John Faris]

Hi Jonathan,

What went wrong before the error? If we could link it to a particular event
then it could be reported as a bug.