>The position of the sys(1016) command is accepted from what i have read, but i can produce it using sys(1011) or windows resource meter (win98 and nt) the memory just keeps getting used up until the app comes to a screaming halt.
>
>with the sample code i accept that you would have to do this a lot but in the real app it takes a form that is open 3 times on a 266 pentuim with 128mb of ram to slow to a crawl.
>
>I have restructured the code to create properties and hold the object reference which seems to be the normal way people do it (from what i have read). this method seems to work fine when in fox (still leaks but not as bad) but when built as an app it seems to loose about 400k each time the same program is run (these are the figures from the real app). This is the major problem the inconsistency between running within fox and as an app!!

Without having something that duplicates your problem, the only thing I can suggest is that you try and "reduce" the memory allocated by VFP using SYS(3050).

There have been instances where I've had very demanding processes that actually benefitted from a reduction in memory available; eg. eliminated "internal concistency errors" in W98 and "Low Memory" conditions in NT.

VFP manages most of it's own memory; what it does is not always consistent with what the OS is doing (IMO) ... particularly with large amounts of RAM ... and 128MB was still "a lot" when VFP 6 debuted.

Reminds me of when I first upgraded my 8088 to 512KB; some of my software went "negative"; eg. 256 - 512 = not enough memory.