No, I've been playing with it quite a bit, in fact, I've used filetostr on the text file and stepped through the entire string returned character by character using asc(substr(lcstring,i,1))... to look at all of the characters. I cannot locate any extra linefeeds that should not be there and even looking at it the last line is on 66 like it should be just before the eject is issued (or form feed in code, etc). It's bugging me...
>Hey - did you see any abnormalities in the text file dump, BTW?
>
>>Ok, I started playing with this, and I've obviously reached brain cramp... what is the easiest way to do a hex dump of an @...say report in VFP? I must be missing something...the only way I can see is to dump it to a text file and then read the file in character by character checking the hex value of every character?
>>
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
