🚀 go-pugleaf

"Charles Kahler" <charles.kahler@lmco.com> wrote in message
news:3FBABB46.1B4B8F2B@lmco.com...
> We have an application with an ADOConnection in a DataModule. Everything
> runs fine, but when we close the application after the ADOConnection has
> been established, we get an access violation. If the ADOConnection is
> never established, we get no error on closing. We have no problem with
> ADOConnections in other modules of the application. I have tried newing
> the ADOConnection component in code as well as putting it directly on
> the DMod. The code looks like this:
>
>  TADOConnection *ADOConnection1 = new TADOConnection(this);

<snip>

In the above, the owner of the connection is 'this', presumably the data
module.  'this' is responsible for deleting the connection.  Below, you say
you delete it.  That would mean it's already gone - invalid - when 'this'
tries to delete it.

Either don't delete it yourself (the easiest) or create the connection with
a null owner:

TADOConnection *ADOConnection1 = new TADOConnection(0);

In this case, your code is responsible for deleting the object.

Hope this helps,

- Arnie

> Connected is later set to false and the ADOCOnnection1 object is
> deleted.
>
> We are using C++Builder 6.0 with sp4. We are running on Windows2000 with
> sp4 installed. In this application, we are running against an Access
> 2000 database, but I believe we have seen the same thing with other
> databases.
>
> What are we doing wrong?
>
> - charley
>