>>we're testing thin client using Hydra beta and everything run fine until our VFP app does a SELECT SQL statement (which only happens in one place, I'm using the boring old methods elsewhere). When the statement begins and the progress bar appears, Performance Monitor shows that all of the available memory (256meg!) is being used by VFP... everything else _and VFP_ come to a screeching halt...
>>
>>when I abort the SELECT statement, VFP holds on to the memory. It doesn't release it until I QUIT.
>>
>>Two questions...
>>1) How to make VFP use less memory (sys(3050) didn't help)
>>2) How to make VFP release the memory when it's finished
>>
>>LM
>
>
>You should report this to the Hydra beta team...as well as the VFP team.

That's a great idea... how do I go about doing that?

Thanks