There is probably not a lot you can do about this. Since the program that is looping through a table and running a VFP EXE is not a data app - why not write it in Visual Basic? This may eliminate the memory leak issue.


>I have developed a system called Remote Man. It simply loops through a table of tasks and spawns another VFP EXE with the parameter of the task to do. This works fine expect after 20 hours of operation it runs out of memory. Microsoft support confirms this error in 5.0 and 6.0 beta but doesn't seem to be concerned with it. The reason I call out to an EXE is that if one fails the others will still execute. Does anyone no a way to get around this BUG?
>Thanks..