Active Connections? (MSSQL)

[crosbj]

I have a vb6 app that connects to a MSSQL 2k server. The app polls the server @ every 6-10 seconds for 3 or so small recordsets. It's used for some machine automation. My problem is this: I open one connection to my db when the app is launched then I use it for my various recordsets. I close and set the recordsets to nothing with each use. If I open MSSQL and look at the Process Info, I will see up to three Process Ids for the machine the app is being used on. This is to be expected since the recordsets are issued all at once. This works fine on every PC except for one. For some reason it will not release the Process Ids and every 6-10 seconds when the recordsets are re-issued it creates new Process Ids which end up being idle. If I run the app on three different PCs I will see up to three Process Ids for two of the PCs but the other one will start at three and just keep growing... I've checked the connection pooling (On). I even rewrote some code to open/close the recordsets with a new connection each time and destroy all and it still won't release the Process Ids on the PC in question. Any other PC reuses the same Process Ids over and over with fresh data returned. They all have the latest MDAC and the app is the same copy on every PC? Is there a possibility I'm having an issue with network traffic? I have to poll the data every 6 seconds because it's used for "real time" conveyor data.

[szlamany]

Just the other day I found some link on MSDN about connections not closing for some reason (ODBC or OLEDB or some other problem - I just barely remember reading it). I'm heading out for the day, so I do not have time to search for it (I looked in my IE history and couldn't find anything immediately...)

Sorry - if I get a chance later tonight I'll try to find the link for you.