Does DBCP handle this issue at all? I realize it's probably some missed statements being closed or something in the application or something, but this is such common problem (just search google for it to see), that I wonder if DBCP makes an effort to help this, like clean things up automatically or anything.
Travis Reeder Space Program http://www.spaceprogram.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
