FTP Time problem

When I compare my local directory structure to the same structure on a ftp server, all my local files are newer. When I take a look at the dates, it looks like this:


file1.xml 03-03-2004 18:43:32 file1.xml 03-03-2004 00:00:00
file2.xml 03-03-2004 18:46:32 file2.xml 03-03-2004 00:00:00


All remote times are set to 0 and all my local files are treated as newer by BC. What's the solution to this problem?

Remote server: IIS 5.0

[Chris]

To force a timestamp copy, use the Touch command.
You can find it on the menu at Actions->Touch.

[Craig]

This is a limitation in the FTP listing that BC gets. It only includes the date portion of each file, so we don't know what the hours, minutes, and seconds are.

There is a new listing format (MLST) that includes a full timestamp, and we're adding support for that in the next BC2 release. Check the log in BC's folder viewer, and look for a response to the "FEAT" command. If it lists MLST, the next release of BC will have full file times.

You can try adding "-T" to the "List Options" edit in the FTP options panel too. Some FTP servers (eg Serv-U) will include more information if that's present, and BC supports it in the current release.

Other than that there aren't any good workarounds besides turning off timestamp checks. We are looking into alternatives for this situation, but none are available in the current release.