Memory issue with VB 6.0 COM component

I have a VB 6.0 dll with an interesting issue.

The .dll opens a Microsoft Jet .mdb having a couple of Jet tables, a couple of ODBC SQL Native Client 10 links to a 2008 database instance on the same box, and a couple of ODBC DataDirect 4.0 links to some Clipper tables also on the same box. The box is Windows Server 2003 running as a VMWare VM.

This .dll has performed without issue on a Windows 2000 server and on a Windows XP development machine.

On the 2003 box, the .dll will complete roughly 70 % of a task involving mulitple adhoc queries with DAO accross these various data sources then the .dll start consuming memory until it runs out of resources and is terminated by the OS.

Where should I start looking for solutions to this kind of an issue?

Patrick
=-=-=-=-=-=-=-=-=-=-=-=-=-

You say VB6 dll, so I assume an AX dll.
Start a standard exe project, then File|Add Project and add your
AX project vbp. Now in Project Explorer click on the standard exe
to select it then Project|References and click on the AX vbp file.

You should now be able to put break points in the AX code modules
and use the standard exe project to put it through its paces.

Thanks VBClassicRocks. The code runs fine on my development machine and on the production server. We're about to replace the production box with a Win Server 2003 box and that's where it's blowing up. I don't have VB 6.0 installed on the Server.

I was able to come up with a workaround that involved making the queries more efficient. For some reason a couple of the queries were much slower on the new box.