LOL!  We've all been there at one time or another!

Dennis

________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Alastair Burr
Sent: Monday, June 07, 2010 6:12 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: "End of Data Encountered" oddity

Thanks Dennis - you can probably guess my initial response to that: it is off 
and, in any case, my program sets it off if, for any reason, it has been 
changed to on.

There is, of course, always one exception when that doesn't apply. I have just 
found that exception. I am just about to take care of it.

Regards,
Alastair.



From: Dennis McGrath<mailto:[email protected]>
Sent: Monday, June 07, 2010 8:32 PM
To: RBASE-L Mailing List<mailto:[email protected]>
Subject: [RBASE-L] - RE: "End of Data Encountered" oddity

Try SET MESSAGES OFF

________________________________
From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On 
Behalf Of Alastair Burr
Sent: Monday, June 07, 2010 2:17 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - "End of Data Encountered" oddity

I unload some data to a file in v7.6 which I then read back with no problem.

In v9.0, however, I have discovered that a line in the output file is added: 
"End of data encountered".

As I trace the process there is no sign that the data written to the file ever 
contains that text.
I create the text and use:
WRITE .vPDV_Action
in the loop to create the file and the watch variable always contains what I 
expect. The program continues then with:

ENDWHILE
WRITE 'RETURN'
OUT SCREEN
DROP CURSOR C1
etc.

The resulting output files looks like this:

Data 1
Data 2...

Data 9
End of data encountered
RETURN
[end of file marker]

Is this a change that I've missed and, if so, how can I turn it off?Strangely, 
I have a vague feeling that I've seen this before some years ago and ought to 
remember.

Regards,
Alastair

----------------------------
Alastair Burr
St. Albans, UK.
[email protected]<mailto:[email protected]>
-----------------------------

Reply via email to