That is just the problem. We do not want to ask the clients (or better, our client does not want this to ask their clients) "This" is the use of signature files. TO us the files size is unknown. Supplier A is uploading files to server B (FTP). We have to make sure that the files are correctly transferred to server C (W2K) We have been thinking of openening the file for write. If a trappable error occurs we maty consider the file being in upload proccess. Any other suggestion or is the signature file really the only way to be sure the file will be correctly transfered. What will happen if the script will start transferring the file (from b to C) while the upload proccess (from A to B) is running. I mean that we start the transfert while our client is uploading the file : If you know the expected file size you can check the size. : For example if you clients provide data files and headers files describing : data file name, size, date, etc... you can use this header information for : file verification. : If files are in a format supporting some kind of a "signature" at : the file end you can check for the presence of such "signature".
|