I have an VFP 6 application that writes to a log file during periodic table updates. I use StrToFile() to write to the log file. If I just let the program run for several cycles over the course of several days I might get an error return code from the StrToFile function. As far as I know there is no other application running that should be touching that log file.

Is there a way to get more info on what happened? Should I use the FOPEN type low-level file functions? I had this same type of error when I tried using SET ALTERNATE commands. I thought that maybe it was a problem with SET ALTERNATE. Apparently it isn't.

Any debugging suggestions or alternate I/O solutions?