Access violation when closing database connection

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Access violation when closing database connection

Post by benek » Sat 31 Oct 2009 11:47

I have upgraded to 3.10.0.8 version. Every time I close database connection an error message occur:

Access violation at adress 06660EF5 in module ibdac100.bpl. Read of address 449200FC
Unknown ISC error 0

Firebird 2.1.3.18
Delphi Turbo

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Thu 05 Nov 2009 11:20

Hello ! Devart Team ! Is anybody here ? :roll:

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Fri 06 Nov 2009 09:23

Well, I uninstalled 3.10.0.8, rebooted machine, would like to install back 3.10.0.7 version
but .. it's impossible.

Setup has detected already installed DAC packages which are incompatible with current version.
Please uninstall DAC products.

Is there a second uninstaller I don't know about ?

Any hints ?!

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Fri 06 Nov 2009 09:46

We could not reproduce the problem. Please send to support*devart*com a complete small sample that demonstrates the problem, including the script for creating database objects.

If you don't have other DACs installed, run IBDAC installation with the /force key:

ibdac310pro.exe /force

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Fri 06 Nov 2009 10:45

Thanks. I've installed 3.10.0.7 successfully. My first success with IBDAC this week. Everything works all right again.

I can't send you "a complete small sample that demonstrates the problem, including the script for creating database objects" because it's too big project and it's definitely not the source of the problem. When I open the project in Delphi IDE with DAC 3.10.0.7 evrything works as it should to, after upgrading to 3.10.0.8 I can't close database connection in object inspector without generating errors. After compliling and building the errors remain in exe file.
Next question I ask myself is IBDAC a proper choice for such scale project...

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Mon 09 Nov 2009 10:05

Please specify whether the error occurs if you add TIBCConnection to a new project, open and close the connection.

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Mon 09 Nov 2009 17:38

In a new project TIBCConnection works all right.

I tried to replace TIBCConnection in my project with a new one but after setting again connection property for all tables, queries and stored proc components the errors continue.

How many components may be connected through one TIBCConnection ?
Is there any limitation ?

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Tue 10 Nov 2009 08:38

There is no limitation on the number of components. When you close the connection all connected components are closed as well. One of these components raises an access violation when closing. Try to link your components to TIBCConnection one by one to find what component causes the problem.

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Tue 10 Nov 2009 10:17

.. but no components except TIBCConnection are opening inside Delphi IDE.
After disconnecting events related to TIBCConnection errors continue...

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Wed 11 Nov 2009 09:17

Maybe this is a problem with the TIBCAlerter component. If you set AutoRegister = True for TIBCAlerter, it starts automatically when you open a connection.

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Wed 11 Nov 2009 12:41

Yeeees! This is the right answer :D
Thanks a lot, Plash.



There's one more question :roll: When the application starts it opens about 80 tables. So far it lasted 5-10 seconds, now it takes ages (or more) or the application hangs dead. I don't say it's because of IBDAC :) but can't find the reason (I didn't change anything related to tables last week)

.. ??

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Thu 12 Nov 2009 09:22

Maybe you have set FetchAll = True for one of the tables.

It is not recommended to open all tables when the application starts. Instead you can open only tables required for a form when you show this form. When you close the form, you can close the tables that were used.

benek
Posts: 20
Joined: Sun 06 Jul 2008 14:22

Post by benek » Thu 12 Nov 2009 17:33

I've found ! It was my fault, I beg your pardon :oops:
Once more thanks for help, Plash.

Post Reply