COMM LINE INPUT - bug or no bug?

[Ketil Krumm]

Having severe problems with COMM LINE INPUT throwing GPFs at me like mad, I searched this forum for an answer.

This statement seems to cause problems in general (i.e. no depending on Windows version or hardware). Is it a bug or is it not?

Using the COMM RECV works fine, but I'd just like to know if I'm doing something wrong...

BTW, Lance made a suggestion in a post from February of pre-filling the receiving variable with spaces. It seemed to solve the problem back then, but it doesn't make any difference on my system (NT 4/SP 6A).

Ketil



------------------

[Jules Marchildon]

As far as I now, no BUG has been reported for that statement.

Please post the relevant code, it is most likely how you are
handling the recv'd data stream.

Regards,
Jules

[Mike Doty]

Are you using #REGISTER NONE?
Do you have a "FLUSH" statement?


------------------