Re: READE reading twice instead on once: why?

==>"The first thing is where in your code is the print that you say is
printing the same record twice..."
I took the EXCEPT line of code and moved it out of the loop (because I was
testing) and then decided to send the loop routine to the list but
obviously the EXCEPT command, because was out of the loop at this point,
was not included, I am sorry for the confusion.

==>"... secondly, when an %eof condition is reached, the buffer containing
the data from the file contains the same data of the last successful read.
This data does NOT get cleared. Why don't you run this code through debug
and follow the logic path Now to go back and get my 16th cup of coffee
(I'm sure that I've missed something in your code)".
Yes, I debugged dozens of times but in reality, I was asking wrong. I
should have used my SETLL, READE and %EOF better. Definitively that
%FOUND was not the correct %BIF to use.

Thanks for the feedback!

PETER VIDAL
MAPICS IT TECHNICAL SUPPORT TEAM / SR SYSTEM ANALYST
10540 Ridge Rd., Suite 203, New Port Richey, FL 34654-5111
Tel:727-849-9999, x2414 /// Fax:727-815-3120
WWW.PALL.COM

"The greater the difficulty, the more glory in surmounting it. Skillful
pilots gain their reputation from storms and tempests."
Epicurus

--------------------------------------------------------------------------------

Attention:

This communication may contain information that is confidential,
privileged and/or exempt from disclosure under applicable law.
If you are not the intended recipient, please notify the sender
immediately and delete the original, all attachments, and all
copies of this communication.


--------------------------------------------------------------------------------