FTP upload of JPG often results in corrupted remote file

[Byron]

I am uploading a JPG file using FTP to a remote server and often the file is
corrupted at the server end. The file size is the same, but the image often
has a block of garbage embedded, or the image goes funky (please excuse the
technical term) from a point to the end of a line, or to the end of the file.
I assumed that the FTP prococol was responsible for error correction, but
the source file is always correct and many of the files arrive at the server
end fine, but often they are corrupted. The files are digital photos < 30k
in length. I am using a trial version of IP*Works and their site has nothing
on the issue. I see nothing in the component that addresses error correction.

Is there any relatively simple way to implement error detection so the file
can be resent if the remote version difers from the local copy?

[Richard L Rosenheim]

Make sure that you are setting the transfer mode to binary. The default
tends to be ASCII.

Richard Rosenheim
"Byron" <By***@discussions.microsoft.com> wrote in message
news:54**********************************@microsof t.com...

I am uploading a JPG file using FTP to a remote server and often the file is corrupted at the server end. The file size is the same, but the image often has a block of garbage embedded, or the image goes funky (please excuse the technical term) from a point to the end of a line, or to the end of the file. I assumed that the FTP prococol was responsible for error correction, but
the source file is always correct and many of the files arrive at the server end fine, but often they are corrupted. The files are digital photos < 30k in length. I am using a trial version of IP*Works and their site has nothing on the issue. I see nothing in the component that addresses error correction.
Is there any relatively simple way to implement error detection so the file can be resent if the remote version difers from the local copy?

[Byron]

Thanks for the reply. I had it set as default, assuming that the server
would figure it out. It dawned on me earlier today to set it explicitly to
binary and I haven't seen the issue recurr since and your reply confirms that
was the right answer. Odd the way it worked probably > 90% of the time set
as the default. You'd think it would consistently work or fail given the
same file type every time.

"Richard L Rosenheim" wrote:

Make sure that you are setting the transfer mode to binary. The default
tends to be ASCII.

Richard Rosenheim
"Byron" <By***@discussions.microsoft.com> wrote in message
news:54**********************************@microsof t.com...

I am uploading a JPG file using FTP to a remote server and often the file

is

corrupted at the server end. The file size is the same, but the image

often

has a block of garbage embedded, or the image goes funky (please excuse

the

technical term) from a point to the end of a line, or to the end of the

file.

I assumed that the FTP prococol was responsible for error correction, but
the source file is always correct and many of the files arrive at the

server

end fine, but often they are corrupted. The files are digital photos <

30k

in length. I am using a trial version of IP*Works and their site has

nothing

on the issue. I see nothing in the component that addresses error

correction.

Is there any relatively simple way to implement error detection so the

file

can be resent if the remote version difers from the local copy?