I feel so stupid!
Quote: "Your problem is the line "i = i+1" in the FOR loop. "
You are quite right that this was a problem but only because I cut and pasted a section of code that I was starting to modify to try something different. The actual code I used did not have the offending line.
What appears to be happening is that Darkbasic is buffering the print output until the double "for loop" has completed before it prints the data. For large input data files this can take some time and evidently I'm not the patient type. For really large files there's probably some cache thrashing going on too which can make things even worse.
The whole purpose for putting the print in a loop like this is a quick and temporary check that data as it was being read in correctly. Sometimes this can be handy for debugging.
It's interesting to note that Darkbasic does not "substantially" buffer print output in a "do...loop".
Has anyone else noticed this phenomenon? Is there a way to turn of the output buffering?