Hi Virusim:

As a bare minimum, and I mean *bare*, if you are using a home brew file transfer do as others have suggested, include a CRC at the end of your message. I've done transfers for years and for anything more substantial than a short message for credit card authorization, I use a standard protocol like XModem, YModem, etc. If you are using VFP on the server side to receive the files then you can use something like CommTools ( www.magnacarta.com ) or Async Profexxional ActiveX ( www.turbopower.com ) to handle one of the various protocols like YModem automatically. No way about it, I would try to use one of these protocols, they are fast, secure, debugged, and easy to implement.

Just my 2 cents worth,

Scott


>>I am creating an client application that will auto dial in to my server
and do some file transfer of any stuff of file.

>>My client is running on Win2k whileas my server might be running OS like
Linux, HP UX.

>>So, in order to ensure that any file transfer is successfully, I do some
checking like ensure that the zip file transfer/any file transfer exist
first and that both source and destination file size are the same.

>>But, it seem like different OS reported different filesize, so how
can I solve this issue to ensure that my file transfer is okay.
I can't use CRC check as not all my files are zip files, even if they
are zip files, CRC check on server side from client side is very slow and
unreliable too.

>>So, anyone had any good ideal to overcome this issue.
Please kindly help and comment on this issue. Thank you.
Best Regards
>>Virusim