This is a typical issue for DataReader. You need to use CommandBehavior Enumeration associated with ExecuteReader in the DAL, something like: oReader = oCommand.ExecuteReader(CommandBehavior.CloseConnection) AND, close the DataReader, in order to close the
connection, after you finish to consume it. Otherwise, there would be a conneciton leaking here. DataReader.close()
MCAD.NET (C#)
MCP on: SQL Server 2k Design&Iimplementation, Web Development (VI 6.0) and VB 5.0
ghan
Participant
1440 Points
288 Posts
Re: Closing connection/SQLDataReader in a n-tier environment
Aug 01, 2003 09:03 PM|LINK
MCP on: SQL Server 2k Design&Iimplementation, Web Development (VI 6.0) and VB 5.0