>Hi Jos,
>
>thanks for your reply.
>
>Is there anything we can do to identify the
>cause of this memory problem?
>
>The developer of the external won't be very happy if we
>just tell them there might be some problem...


Hi Erwin.

The only thing I can tell you is that in every situation where I had a "runaway" memory problem it was always the cause of something outside of VFP itself i.e. a third party dll.

VFP memory usage is, as far as I know, 100% ok with no known memory leak issues at all. We run systems 24/7 for round the clock real-time market trading which use external dll's for a variety of functions.

You could try "proving" it must be the DLL by running your app for a non-stop period of time but do not call the dll at all. Simulate the dll call instead with a dummy routine/dummy data. Run this simulation for a period of time long enough to show a static memory condition vs. the dll version increasing memory condition.

Make sure you implement SYS(3050) anyway in both systems, which is good practice.