use double > to append to the output file. A single > overwrites output file if it exists.

myftp_command_here > output.log && overwrites or creates new file
myftp_command_here >> output.log && append to existing file, if exists

>Ok, that would be the easiest thing to do. Tell me, how can I redirect output (I vaguely remember >> command, but give me a correct syntax, please). Thanks in advance.
>
>>An easy solution, since you are already using the DOS FTP, is to just redirect the DOS output to a logfile. You can then use the information in RFC 959 (found at www.rfc.net) to parse the log file for the FTP codes. Particularly, you are looking for codes 125 (transfer starting), 150 (opening data connection) or 200 (command okay) followed by the code 226 (transfer complete). RFC 959 has a more complete list of FTP codes.
>>
>>One thing to keep in mind with the DOS FTP is that it cannot do PASV mode, which some FTP servers may require. This has been a recent problem for me.
>>
>>
>>>Hi everybody,
>>>
>>>I got an interesting assignment ysterday: write an Output Module. IOW, we can produce files in the format, what customer desires, now we need to deliver this file to customer. It code be done in bunch of ways: file could be transfered to them using ftp (the simplest case), e-mailed to them, delivered by regular mail on disketts or CD, etc.
>>>
>>> I'd like to start from ftp. My questions is: what the best way of doing ftp. It's not necessary should be within VFP, currently we run a simple bat file, like:
>>>

>>>rem Send file, then move ftp file to SentFtp subdirectory
>>>ftp -s:ftp0713.ftp
>>>move /Y ftp0713.ftp SentFtp\ftp0713.ftp
>>>exit
>>>

>>>and ftp0713 would contain the necessary directives. Very simple. But I'd like to have better control of this process. How can I, for example, be sure, that files were actually sent?
>>>
>>>So, basically my question is: what would be the best program for ftp files non-interactively with giving us as much control as possible, e.g. suppose, it would send 20 files to 20 different places. File 1, 5 and 8 could not be sent for some reason. The program would not stop, would run other files, and then try to repeat process for these files. It gives us summary report (log file) at the end of the process...