Hmm...following the upgrade to VS.NET 2003 and the concurrent upgrade to 1.1 this required, an odd bug has surfaced in my code - it appears to be some form of connection leak. This is a bit odd as I've been using the same code and the DAAB with a connection string only (which should close the connection once the reader is closed - in the case of SQLHelper.ExecuteReader).

Keep you posted...hopefully its' just a bit of errant code not shutting the connection down...hopefully...

P.S. If anyone else has experienced anything like this, please email me at scott@mostlylucid.net ta...