I get this in a sort of batch program that is scheduled to run hourly on a W2K Server.

The program appends CSV files into a cursor, does some aggregations and puts the results in a SQL PT structure.

The program can run for hours without problem and the suddenly crash.

The offending program line is not always the same, and there does not appear to be a programatic error in the code.

I have the feeling it has sometings to do with VFP memory handling.

I guess my questions are:

In a loop, is it better to (re)-create and destroy a class or is the soundest approach to create it outside the loop, call it for everey pass and then destroy it?

SCAN
   oMyObject=CREATEOBJECT("MyObject")
   oMyObject.DoThis
   oMyObject.DoThat
   oMyObject.DoTheOther
   RELEASE oMyObject
ENDSCAN


Or the one I use at present


oMyObject=CREATEOBJECT("MyObject")
SCAN
   oMyObject.DoThis
   oMyObject.DoThat
   oMyObject.DoTheOther
ENDSCAN
RELEASE oMyObject



Will SYS(1104) -Purge memory help?

I have put a SYS(1016) on the screen, and the numbers go up and down a bit, but as a whole seem fairly stable. 

In any case, how does one identify memory leaks and fix them?

TIA

Peter Pirker


Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?

(Woody Allen)