----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Friday, March 07, 2008 11:27 AM Subject: [RBASE-L] - Re: NOTE, VARCHAR, and LINEEND.
> << > Before you chase the Control as the issue, be sure the data contains the > correct values. >>> > > I'll pull out the ASCII chars in a moment -- although I'm fairly sure the > UPDATE commands I used to try the three different possibilities CR, LF and > CRLF) worked properly. Also, I forgot to mention in my original post -- the > fields after conversion to VARCHAR display correctly in printed reports, it's > only on the form that I'm having trouble achieving the results I want. > > However, note that when I simply redefined the field from NOTE to VARCHAR the > behavior of the Memo control changed -- unless you think the redefinition > also change the lineend character in the text? I guess that's possible. > > BTW, what _IS_ the correct lineend character? 13? 10? or 13 + 10? In the VarChar data, I always use the combo 13 + 10, which will work pretty much anywhere as the systems that don't use the combo, still use the LF (10), so the result in output is still the same. On an old 6.5 db here, lineend was set to Char(254) as well as the current db I am using internally. As far as what is the correct LineEnd char, it seems to me that whatever (within reason of course) you set as the lineend, it is going to have the effect of substituting whatever the engine is using internally for that character regardless. There were some issues with this midstream in 7.1 I think, that were resolved satisfactorily and I haven't seen a reccurance of any anomolies since (LineEnd doubling ISTR). > Back at you in a few minutes with that ASCII info. > -- > Larry > > >
