Figured it out myself.

I needed in the destroy of the data environment the SQLDISCONNECT() statement to kill the connection manually. Now when I open the form, I get two connections and when I exit the form, the two connections are disposed of.

The other thing I was doing wrong was recreating the connection string each time BeforeOpenTables was called. Instead I have put code in to ignore the SQLCONNECT() if there is already a data handle there.



>I have created a new form based on business objects, data objects, collections and cursor adapters. The form works great! But I have only a single problem.
>
>The cursor adapters are creating new inactive connections to the Oracle database. For example, when I open the form it creates two. Moving from one record to another creates another one because a query is performed to get some support info from the database. Because I didn't know this was going on, I inadvertantly used all 500 connections to the test server, bringing it down!
>
>Now I am looking into this further and noticed that after exiting my application and explicitly DESTROYing each cursor adapter, data environment, collection, business object etc, the inactive sessions in Oracle still persist. Only after exiting Visual FoxPro completely, do these inactive sessions get removed from the Oracle database.
>
>Does anyone have any kind of solution for this?
>
>Each business object has it's own data environment object. Each data environment object creates a new private data session. Within this environment, the cursor adapter is added.