Sounds like you are not using "Time Based Name". Try turning that option on as a test, and see if things get better.

How are you determining that the file isn't geting updated? If you are going by what the AbelCam Logger says - don't! If the uploaded file always has the same name, the logger does not seem to show every upload. I'd assume it is tossing out what it believes to be duplicate log entries.

You may also need to use a time period >15 seconds. I just tried your settings here and the timing got a bit erratic at 15 sec. Worked better at 30 sec. Could be my FTP server's fault though. Otherwise it worked fine with both the Public version (2.1.0) and the latest Beta version (2.1.1 - 4 Apr build).

Just keep in mind that if you use something like "cam.jpg" instead of Time Based Name, the only way you can tell for sure if it is updating is to periodically check the contents of the file - perhaps by pointing a web browser at it and hitting refresh a lot. The logger can not be fully trusted, nor necessarily can the timestamp on the file on the FTP server.

I understand why timestamp naming won't work for your application. My main reason for suggesting it was just that it would make a good experiment to get to the bottom of what's really going on. With timestamp naming the filename obviously will be different every time, which means that Logger will show every single FTP upload attempt instead of only the first one. (there is a feature in the logger that causes it to not display what it believes to be duplicate messages - bit of a double-edged sword perhaps) Also with timestamp names you will be able to see the files accumulating on the server.

Then again, this could be some kind of Vista-specific issue in the AbelCam software, in which case I'm not going to be able to be very helpful. The software doesn't "officially" run on Vista yet but quite a few people do seem to have gotten it to work. My understanding is that SSE is working on getting the code Vista-compatible now.