>First, just to be clear, your call is probably to SYS( 1104 ) rather than SYS( 1004 ), right?

Yup. Sorry... mistyped.

I'll check out this Process Explorer. Thanks for the tip!
-- John

>>
>>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!
>
>First, just to be clear, your call is probably to SYS( 1104 ) rather than SYS( 1004 ), right?
>
>Next, have you checked which process(es) is increasing its RAM usage? A very useful tool is Process Explorer (formerly from SysInternals, now a part of MS): http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx
>
>This tool has the advantage that it shows memory usage by individual services running within a single SVCHOST so you can spot the culprit. You can't see this with just the Task Manager.
>
>If necessary, it's possible to limit the amount of RAM used by some processes, such as SQL Server instances and IIS.
>
>Finally, rebooting the server periodically is a drastic step. If you can find the problem process, you can probably just stop, then restart that process rather than the whole server. Set up a .CMD file with the appropriate NET STOP and NET START commands and schedule that ( CMD /C MyProcessRecycler.CMD ).