Hello,

We are starting a new beta-cycle for a new 2.2 release of WF soon. I will make sure the handling of timestamps will get proper attention.

I have not looked at it yet, but I *think* WF uses UTC (which may defer a little from GMT sometimes).

One issue I already see with this.... Different "local times" depending how you run the task (as a Service vs "normal" app).
Another issue: FTP server is in another timezone, how should WF map those timestamps.....

Anyway, I will look at it further.

Gert

Do you have some samples? Show the timestamp on the FTP server as reported by an FTP client and the corresponding timestamp that WF creates?

If I change this and your local time is "older" than the FTP server's time, it may get tricky for WF to get it right.... When it scans the FTP server again, WF may think the file is updated on the FTP server and start downloading again, tricky.

But I am not sure, I will have to look further into this.

One thing you can experiment (!!) with now is to use the "run a batch file" action for the downloaded file and set the timestamp from there. You would need a command line program to set the timestamp, I am sure there are lots of them available - probably in the Windows Resource Kit.

Gert