>Hrm... I would've thought that FOPEN() before the processing loop, then FWRITE()/FPUTS() each record in the processing loop (i.e. leaving the file open within the loop), then FCLOSE() after the loop would be faster than using strtofile() for each record within the processing loop. If there is an antivirus involved, using LLFF would avoid triggering a scan with each loop iteration, whereas the implicit open/close with strtofile() would likely trigger a file scan each record.

When writing oodles of text, going via COM and FileSystemObject was faster than vfp LLF in a special application (we had to add that option for writing files beyond 2GB and found it faster for large files below 2GB as well). NOT tested systematically for specific amounts of data and/or writing paatern, just 1 data point.