>>>>Hmm - I'm only interested in straight text. The EditBox isn't bound so I wouldn't have thought 'Value' comes into it (although I could be wrong :-[)
>>>
>>>Just to be certain: you mean both Editboxes are not bound ?
>>
>>Ah. The first Editbox (which adds the linefeed) is not bound - the Value property is set in a method.
>>The second is data bound to a memo field in a VFP table. Still stuck on understanding how this might affect things tho.
>>
>>Docs say VFP inserts linefeeds 'when user code reads the Value property' (I'm not doing this) or when 'the EditBox loses focus' (which,AFAICS, it does not).
>>
>>Must say this smells like a bad design to me - why didn't they just add the linefeeds to the Value 'get' and NOT mess with the text buffer itself ?
>>And, IAC, why, in the first editbox, isn't the linefeed added immediately after the CR is typed rather than when the next character is entered.
>>
>>Interested to know what you see. I've just stuck the following code in the InteractiveChange event:

s = THIS.TEXT
>>FOR x = 1 TO LEN(s)
>>DEBUGOUT ASC(SUBSTR(x,1)
>>ENDFOR

>
>no time to horse around here ;-)
>but I was just wondering on your wording and speculating from FPD / FPXenix history if the Unix/Windows different CR/LF conventions come into play here in the historic parts of the code if one of the Editboxes is bound and the other not. Just a very wild guess from subconscious....

Yes - I guess it exists since SCO FoxBASE compatability was needed...

No time to horse around here either - I'm loading up for two weeks cycling in Europe :-}