VB Forum / Database Access / October 2006

You likely got here by using the web interface which merely lists the group
as "Databases", but this is a classic VB (VB6 and lower) newsgroup. Your
post will likely fall on many deaf ears as your first line includes "VC++".
You probably should seek out a VC++ newsgroup. Or better
"microsoft.public.sqlserver.dts".

You failed to mention the database/s you are using. One can assume SQL
Server, but then you mentioned "Jet OLE DB", so I guess it is really
MSAccess???  (But that doesn't really matter. <g>)

Bottom line - DTS often leaks. How bad and where seems to be linked to
particular providers, cursors, and creating and destroying connections. The
'cure' is no different from any other memory leak - try to isolate the exact
location (item) that is leaking and then reworking the architecture to
specifically clean it up. The fix may range from simply keeping one
connection for the life of the app, to moving DTS operations off into some
other process which can be periodically explicitly destroyed.

Using VC++ you have debugging and tracing opportunities available to you
that VB doesn't have out-of-the-box. That is why I suggest a VC++ group may
be more helpful.

hth
-ralph