When I make a new dataaccessadapter with 'new DataAccessAdapter(true)' and make a bunch of stored procedure calls, the DAA is not keeping the connection open between stored procedure calls as I thought it was supposed to do.

When I trace the code, the connection never actually gets opened, except for possibly inside 'adapter.Fill(dataSetToFill)'

Am I doing something wrong?

Can you post your code that is causing the behavior?

You should open the connection manually first, then do the calls then close it again. This is for procs only. Other LLBLGen Pro code leaves the open/close of the connection to the dataadapter used.

Otis wrote:

You should open the connection manually first, then do the calls then close it again. This is for procs only. Other LLBLGen Pro code leaves the open/close of the connection to the dataadapter used.

I guess my question is why?

The connection object is protected within the DataAccessAdapter, so it makes this impossible to open it from the outside. How would you suggest doing this? Right now I've just changed the DAA template code to open the connection if it isn't already open inside CallRetrievalStoredProcedure.

The connection object is protected within the DataAccessAdapter, so it makes this impossible to open it from the outside. How would you suggest doing this?

Using the DataAccessAdapter OpenConnection() method.

Walaa wrote:

The connection object is protected within the DataAccessAdapter, so it makes this impossible to open it from the outside. How would you suggest doing this?

Using the DataAccessAdapter OpenConnection() method.

Whoops! Missed that one