>>Do you have any shared properties or methods in your Framework.Framework.Data class? This could cause these kinds of problems.
>
>Shared has been gone since a very long time. There is no instance of that keyword nowhere in the application.
>
>But, I was looking at message #1150765. Viv mentioned in that message that if two objects are being instantiated from the same class that they are in fact using the same instantation. If yes, that would be the cause of my problems. But, to me, if I do this:
>
>

>        Dim loDataProviderFederation As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>        Dim loDataProviderMaster As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>        Dim loDataProviderSchool As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>        Dim loDataProviderStyle As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>        Dim loDataProviderStyleDefinition As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>        Dim loDataProviderWeapon As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>

>
>I always thought each of those objects were being instantiated in their own Framework.Framework.Data environment. But, when I read his message, it doesn't seem to be the case.
>
>Basically, how I can adjust to make sure that whenever I create an instance of a class that it will be independent and not shared across the application?

Michel,

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.