>>I haven't read all of this thread so I don't know if this has been brought up already. It sounds like some of the objects within your data provider are hanging around a lot longer than you expect. I mean, while the connection objects might be waiting around for garbage collection another object may pick up the faux-closed connection. I have seen SQL Server hold a connection until the garbage collector disposes the object.
>>Perhaps temporarily adding an event log entry in the Disposing method will help to isolate the problem.
>
>I am using VFP as the backend. Is there a way to enable an event log for that? Also, based on this, I am not sure exactly what I would have to do to verify for that.

I was thinking of writing to the system event log inside of the Dispose method of your provider class. To do it you will have to override the Dispose method in the class definition. The date & time is already part of the log, so anything that can identify the individual instance of your class and also connection.State is sufficient for the log entry. Then you can see exactly when the objects that are connected to the database are destroyed. Maybe there is a correlation between objects remaining open and the errors that you are seeing.

This idea comes from working with SQL Server, so it may not be applicable to VFP.