Ahh, see, I was missing the point. The report is generated from whatever is in the BDS file at the time the D.Report command is issued, so it's always in synch with the current BDS. That does mean that I'll have to be careful with the log between runs of different files, or I might overwrite one. Thanks, Thom.
Henry Taylor
Technical Analyst II
Lutheran Health Network
Ph. (260) 425-3914
"Thom C. Blackwell" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 05/05/2005 01:57 PM | To: <[email protected]> cc: Subject: RE: [Talk] DataStation log files |
Greetings,
The BDS file is the place where records are retained, the D.Report command will read the BDS file to generate the .Log file â so each time D.Report executes the .Log file would indeed be overwritten. However the information within the BDS file would not be âoverwrittenâ. The only time record retention would be cleared when the file modified time changes â or of course if you deleted your BDS file.
Hereâs an example for setting up a script for reprocessing â this would skip over any record that had a Status set.
Sub FileProcess
Do
If d(âStatusâ)=ââ then
ProcessDataRoutine
End if
D.Next_
Loop until D.EOF
End if
End Sub
Sub ProcessDataRoutine
â
D(âStatusâ)=âDoneâ
End sub
Sent: Thursday, May 05, 2005 2:43 PM
To: [email protected]
Subject: [Talk] DataStation log files
Am I seeing things correctly? Do the .log files created from the D.Report command overwrite each time, even if the processing is simply a continuation of a previously started file? If so, then that means that you cannot restart a process - if it abnormally aborts, for example - and retain any records logged prior to the point at which it stopped. Is this correct? Or am I missing something?
Henry Taylor
Technical Analyst II
Lutheran Health Network
Ph. (260) 425-3914
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
<<inline: pic09961.gif>>
