Hey FoxFolx!

We've been battling a memory leak and I wondered if anyone had any ideas.

Here's the scenario:
MS-SQL backend, VFP middleware using SPT, no DBC and/or views (well, SQL views grabbed into VFP, but not a remote view inside a DBC). Attached to the SQL via an ODBC driver and putting out West Wind (Web Connect) HTML pages.

A lot of the work utilizes DHTML renders of VFP screen forms, some of which are relatively extensive, multi-page forms (render times about 3 seconds).

Anyway... a reboot of the server cleans it up, and a workaround for now has us rebooting it every hour. If we don't, the client screen starts at about 3 seconds and on every render slowly builds up -- to over 30 seconds! A look at the West Wind log shows memory utilization being slowly gobbled up (until it starts using virtual memory).

Here's what we've tried:
Making sure temp files aren't building up soemwhere.

Ran memory and object dumps to file every x minutes to a file and compared. Nothing different, other than the object values.

Ran this code as per 'FoxPert.com' (thanks Christoph!):

lnNot = SYS(1004)
lcMemory = Sys(3050,1)
Sys(3050,1,1)
Sys(3050,1,Val(lcMemory))

It didn't change the 'memory creep'. Does anyone have any ideas? Is it possibly NOT the VFP, but the ODBC? We're out of ideas and hoped the "it takes a (UT) village" approach might work. Thanks in advance!