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
=-=-=-=-=-=-=-=-=-=-=-=-=-