Having been in this EXACT situation before, I would guess it has 
something to do with how you're interacting with the SQL Server. In my 
case, we went over our connection management with a fine toothed comb 
and found some connections and recordsets that were not being closed and 
cleared properly.

We also converted the T-SQL data access I was using to stored 
procedures. Went from a vicious resource hog to a lean, mean SQL app in 
a few days.

-----Original Message-----
From: Michael Kovac [mailto:mkovac@n...]
Sent: Friday, March 07, 2003 10:35 AM
To: professional vb
Subject: [pro_vb] VB program uses 89% of system resources in Windows 98


We just finished a program of medium complexity, in VB6, and running it
under Windows 2000 or XP while any other applications are running is no
problem. The application is managing data on a SQL server, consists of
one exe and two small Dlls.

Starting the Program in Windows 98 gave us an out of memory error (on a
recently purchased  1.8GHz P4 desktop w/256MB ram). After some checking
we found that GDI resources were chewed up by too many controls and
picture boxes. After reducing the number of controls and building 
control
arrays, GDI is now at a comfortable 89% free when the application is
fully loaded.

System resources and user resources(as displayed by the Windows 98
resource meter), however, drop from approx. 85% free before starting the 

app to only 7% free while the app is loading and goes to about 11% free
when it is done loading.

Needless to say, we are lucky if we can run the application at all on 98 

as most clients have AV and other stuff running in the background.

What should we look at in the code to reduce the amount of system and
user resource eaten up in Windows 98 by this application?

Many thanks...