🚀 go-pugleaf

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);
 ADOConnection1->CommandTimeout = 30;
 ADOConnection1->ConnectionTimeout = 15;
 ADOConnection1->ConnectOptions = coConnectUnspecified;
 ADOConnection1->CursorLocation = clUseClient;
 ADOConnection1->IsolationLevel = ilCursorStability;
 ADOConnection1->KeepConnection = true;
 ADOConnection1->LoginPrompt = false;
 ADOConnection1->Provider = "Microsoft.Jet.OLEDB.4.0";
 ADOConnection1->ConnectionString.Empty();
 AnsiString conStr;
 conStr.sprintf("Provider=Microsoft.Jet.OLEDB.4.0; Data Source = %s;
Persist Security Info=False",
   d:\\data\\datab.mdb );
 ADOConnection1->ConnectionString = WideString( conStr );
 ADOConnection1->Connected = true;

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