Back to product page

TransferMode property


Determines if transfers are Binary or AscII.

Type

A TransferModesEnum enumeration. Determines if transfers are Binary or ASCII.

Syntax

  • Basic
object.TransferMode[= value]
The TransferMode(object,value) syntax has these parts:
objectAn expression evaluating to an object of type wodFtpDLX.
valueA TransferModesEnum enumeration, as described in settings.

Remarks

Settings

The settings for value are:

Constant Value Description
Binary0 Uses binary mode data transfer.
AscII 1 Uses ASCII mode data transfer.


TransferMode property is a client-side add-on (by default SFTP protocol does not make a difference between ASCII and BINARY transfer modes, but FTP does) property. When set to Binary, wodFtpDLX will not interfere with the file content sent or received from the server. However, if set to AscII then wodFtpDLX will newline translation to CRLF, LF or CR, based on AscIITranslation property setting, both for uploads and downloads. As a result, ASCII files should be readable both on remote and local side.

This property makes sense only if remote system is UNIX or similar OS. If server is also Windows based, you should make no translation because both systems use same sequences to mark EOL (end-of-line). However, UNIX systems don't use CRLF (carriage-return-line-feed) but only LF (line-feed).

Please note that when receiving a file using ASCII mode, Progress event will show false information regarding file size/position. It will show information which is valid for a file on remote server, but when downloaded it can be much larger (depending of number of LF's found inside).

Resume property can cause trouble when used in ASCII mode because most probably resume will occur on different places on local/remote side.

Platforms

Windows