Detecting End-of-File using READLINE command

[George Simon]

Do you see any vertical lines in this message?
I don't.  I see the text of your last post indented because Word cannot
quote with ">".
I'll try it again without Word as the editor.

George Simon (IT Department)
American River Logistics, LTD
614 Progress St.
Elizabeth, NJ  07205
Phone:(908)354-7746      Fax:(908)354-7491
mailto:george at worldest.com
http://www.americanriverintl.com/



-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of John Esak
Sent: Tuesday, September 14, 2004 12:23 AM
To: George Simon
Cc: filePro mailing list
Subject: RE: Detecting End-of-File using READLINE command

George.
Hi. Okay, I'll really try and work this out with you... but we have to get
to square one first... The message you posted below looks fine, yes. But 99%
of all your other messages do NOT. You say you have no trouble quoting HTML,
but you most certainly do.

Maybe you should read some of the messages you post here. The one I replied
to in particular (the first time I mentioned this in this thread that is)
did NOT have any >'s... none.  What it had was a long vertical line down the
page next to the message you "thought" you were quoting. It does NOT show up
in any of our mail clients a >'s... Now, when our mail clients try to reply
to you and quote that sort of stupid looking long vertical line... all they
do is indent it and start out "our" typing with a long vertical line next to
it as well.  It is all VERY frustrating, so we "convert" your messages to
plain text which removes the ling vertical lines... but this conversion can
only be done after we have hit the (R)eply button... so, therefore, we hae
NOT put any >'s next to what has just been converted. ... and we certainly
aren't going to add these one at a time.

Before I can help any further with this... I have to believe that you
understand you are presenting with a problem... rather than denial, thinking
that there is nothing wrong.

So, let me know if you now understand the problem? All the time you think
you are "quoting" with >'s you are putting long "impossible-to-deal-wtih"
vertical lines.

John


> -----Original Message-----
> From: George Simon [mailto:flowersoft at compuserve.com]
> Sent: Monday, September 13, 2004 11:51 PM
> To: john at valar.com; filePro mailing list
> Subject: Re: Detecting End-of-File using READLINE command
>
>
> The reason it was indented is because I was using Word as the email editor
> in that computer and Word cannot quote (>), so it indents instead.
> On this computer, I'm not using Word as the email editor and the quoting
> looks fine to me.
> My question was how come people claim to have problems quoting html
> messages, when I do not.
>
> ----- Original Message -----
> From: "John Esak" <john at valar.com>
> To: "filePro mailing list" <filepro-list at seaslug.org>
> Sent: Monday, September 13, 2004 8:19 PM
> Subject: FW: Detecting End-of-File using READLINE command
>
>
> >
> > George,
> >
> > You just made my point SO clearly... Not only did you NOT quote his
> > message... not even close... all you did was indent it... but, you then
> > through this giant image as well into the mix.
> >
> > Believe me, you are not going to make any friend on this list
> that way...
> > also, most people will not even bother sending you a response.
> Why is it
> so
> > hard to understand that most people on this list prefer to see
> messages in
> > plain text and accommodate them?  The mechinism exists in
> Outlook to mark
> a
> > particular recipient as one that gets "plain text" only. So, it
> certainly
> > wouldn't be hard to do.
> >
> > Anyway, just will keep top-posting to messages that can NOT be quoted...
> >
> > Sorry, but at least I'm not so ademant about plain text that I
> won't even
> > resond. You can keep using it... but you certainly will be pissing
> everyone
> > off on this list... and too be honest, I would have to agree that they
> (the
> > big "they" out there) have asked several, maybe 20 or 30 times
> that people
> > only use plain text here.
> >
> > John
> >
> > P.S. - I have converted your response below to show you exactly what is
> > meant by plain text... Compare it with your offering... :-)
> >
> >
> > -----Original Message-----
> > From: filepro-list-bounces at lists.celestial.com
> > [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
> George Simon
> > Sent: Monday, September 13, 2004 4:52 PM
> > To: John Hemmer; filePro mailing list
> > Subject: RE: Detecting End-of-File using READLINE command
> >
> >
> > Hmmm. I don't have a problem quoting his message.
> >
> > George Simon (IT Department)
> > American River Logistics, LTD
> > 614 Progress St.
> > Elizabeth, NJ  07205
> > Phone:(908)354-7746      Fax:(908)354-7491
> > mailto:george at worldest.com
> > http://www.americanriverintl.com/
> >
> >
> >
> > -----Original Message-----
> > From: filepro-list-bounces at lists.celestial.com
> > [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
> John Hemmer
> > Sent: Monday, September 13, 2004 12:08 PM
> > To: filePro mailing list
> > Subject: Detecting End-of-File using READLINE command
> >
> > When using the READLINE command to read sequential records
> > e.g.
> >
> >     bytes=READLINE(handle,destination,length)
> >
> > When a line consists of just a newline character, the number of
> > bytes read and returned in "bytes" may be zero. However, there
> > could be many records that follow this line.
> >
> > How can I detect the EOF, End-of-File?  Is a negative number
> > of bytes returned?
> >
> > None of the Documentation I have, STN Manual, Online FilePro
> > help, etc,  answers these questions.
> >
> > TIAA
> >
> > John
> >
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list