Hello All,

There is a bug in ALINES() that periodically causes a GPF in VFP.

This occurs only when the default delimiter is used, i.e.

ALINES( laArray, lcString ).

If a delimiter other than the default delimiter is used, i.e.

ALINES( laArray, lcString, .F. "," ),

it does not occur. The use of the third parameter to trim the resulting array seems to have no effect, nor does declaring the return array before calling ALINES().

It does not always occur -- it is periodic and random. I have not yet been able to isolate the environmental condition(s) that must exist for it to occur but here is what I know as of this writing:

(1) It occurs in Win XP Pro, Win 98, and Win 2000. I have not test other OSs but it appear to be OS independent.
(2) As indicated above, ALINES() must be called without specifying a delimiter. Even if CHR(13) is specified as the delimiter, it does not appear to occur.
(3) The string to be translated must contain at least one CHR( 13 ) or CHR( 10 ) character.

The work-around for now is never to call ALINES() with its default delimiter. I have not yet seen the failure unless the default delimiter is used.

If anyone else encounters this issue, please let me know as much about it as you can. I would like to nail down the environmental condition(s) that cause the error if I can before I report it to VFP.