>>>Hi Peter,
>>>
>>>MS consider this behavior as "by design". You may add your rating to Improve ALINES() flexibility, regarding delimiter and empty element behaviour Wish #880
>>
>>Hi Sergey,
>>
>>Thanks for the reference. I've added my rating and also a comment (don't take it personally, I'm really grateful for your reply :).
>>
>>Comment: If the last 'line' is empty, then it's not added to the array. Sergey Berezniker says that MS claims that it's 'by design'. However, it cannot be by design, because it's not documented! Also, in VFP6 empty 'lines' in the rest of the array were forgotten to add to the array too. That 'behavior' has been repaired in vfp7. This is a clear indication that the repair must be looked at one more time!
>
>Hi Peter,
>
>It depends on how to count lines. According to help, the cParseChar parameter (by deault it's CHR(13),CHR(10) and there combinations ) "specifies one or more character strings that terminate the elements in cExpression". In your example

lcC = "a" + ccCRLF + "b" + ccCRLF + "c" + ccCRLF + ""

>there's only three ccCRLF which terminates three elements and there's nothing after the last ccCRLF.

Hmm, I understand what you're saying. One reply: You use the word 'terminate'. However, this word in the definition would cause all text after the last delimiter to be not copied. The documentation uses the word 'delimit' and that's what you obviously really mean.

Thanks for the explanation of the MS-view. :)