Thank's guys,

Jos,

I've tried your suggestions, and they seem to slow the memory leak down, but do, as far as I can see, not eliminate the problem.

Since this all happens just by the following sequence:

Load Form1
Activate Form1

Load Form2
Activate Form2

Activate Form1
Activate Form2
Activate Form1...Activate Form2...1,2,1,2, a.s.o.

1) Flush solution does not apply, nothing is written to disk, the other suggestions are implementet.

2) Paul: Reindexing does not apply, I'm using remote views against SQL Server only.

3) Yh Yau: Remove memory? I do have more than 256MB, should I really physically downsize? This is VFP 8.0, we're in the 21st century, are you serious?

I've put in lot's of Try...Catch To oException...Endtry statements.
Is there any point in explicitly setting oException and other variables to NULL and releasing them manually?

Anything else I could do?

BR & TIA






>>In the explanation for the error it says:
>>
>>Free some memory currently in use and try this operation again.
>>
>>Yes,I'd love to, but which memory? Where? How? :)
>>
>>All I can see is, that the app- (VFP 8 SP1) - gobbles up memory when I activate / deactivate certain windows, but I cant' seem to pin it down to anything specific.
>>
>>Any and all suggestions are appreciated.
>>
>>TIA
>
>Peter, check out SYS(3050) and SYS(1104) functions and FLUSH command which should help.