Specifying files and folders

Specify files so that they can be identified by the local machine. The name can be a file or a folder. Mapped drives cannot be used. The file names are the absolute path to the machine for both local and remote.

• Source or destination locations can be a file or folder. These rules apply:

  • If the destination is a folder, then all sub-folders and files inside the folder are transferred.

  • If a destination folder does not exist, it will not be created and an error message will be sent.

    To create a new destination folder, add a backslash at the end of the file path, for example, C:\TestingDirectories\FTP\DestinationFolder\. By adding a backslash, a new folder called DestinationFolder will be created in the FTP folder.

  • If source is a file and the destination file name is different than the source file, the source file name will be changed to the destination name during the transfer.

  • Front or back slashes can be used in file paths.

  • Both absolute and relative paths are supported.

  • UNC names are not supported

• Wild cards can be used. If they are used, these rules apply:

  • If a source is a folder or contains a wild card, the destination cannot be a file.

  • Wild cards are specified using the asterisk (*) character.

  • If a wild card is used in the file name, then all files and folders matching the name are transferred.

  • If the source contains a wild card (or is a folder), the destination must exist. If it does not exist, an error message will occur.

These are file path/name examples:

• file://home/UserName/UserDir/File.txt

• file:///C:/Documents and Settings/File.txt

• file://///HostName/ShareLocation/ShareFile.txt

• home/UserName/UserDir/File.txt

These examples are not supported:

• <MappedDrive>:\program files\UserDir\File.txt

• <MappedDrive>:/program files/UserDir/File.txt