Reflection Desktop VBA Guide
Attachmate.Reflection.Objects.Emulation.OpenSystems Library / Attachmate.Reflection.Objects.Emulation.OpenSystems Library / FileTransfer Object / TransferIfFileExistsDefault Property
In This Topic
    TransferIfFileExistsDefault Property
    In This Topic
    Returns or specifies what happens with transfers from the File Transfer dialog box if the destination file already exists.
    Syntax
    expression.TransferIfFileExistsDefault As DestinationFileExistsOption
    where expression is a variable that represents a FileTransfer Object

    Property Value

    A DestinationFileExistsOption value
    Remarks
    This property is automatically set every time you perform a transfer from the File Transfer dialog box and the value becomes the default for the next transfer from the dialog box.

    This property has no effect on programmatic transfers. If you don't explicitly specify an IfFileExists action when you transfer files programmatically, the transfer fails if the destination file already exists (equivalent to DestinationDestinationFileExistsOption.Cancel).

    This property affects transfers under all supported protocols.

    • Appends the contents of the source file to the end of the destination file.
    • Prompts the user to specify what should be done. (The default.)
    • Fails the transfer.
    • For transfers to a host, deletes both the contents of the host (destination) file and its attributes. For transfers from the host, DestinationFileExistsOption.Delete replaces the local file.
    • This value is host specific and is relevant only for WRQ/Reflection transfers:

      For transfers to an HP 3000 host, replaces the data in the destination file, but does not replace the file's attributes (characteristics). Overwriting a smaller file with a larger one can be problematic as new records are not allocated to accommodate additional data and only part of the file data is transferred. Use DestinationFileExistsOption.Delete to avoid this problem.

      For transfers to a VMS host, replaces only the most recent instance of the destination file.

      For transfers to a UNIX host, preserves existing symbolic links to the host file.

    • This option is available when you use the WRQ/Reflection protocol, and when you're connected to a VMS host or an HP 3000 host. (With an HP 3000 host, this option is equivalent to DestinationFileExistsOption.Delete).

      If you send a PC file to a VMS host using the DestinationFileExistsOption.Purge option, existing versions of the file on the host are purged following the transfer. For example, if you send NOTES.TXT to the host, and NOTES.TXT;2 and NOTES.TXT;3 already exist, a successful transfer results in a single file on the host called NOTES.TXT;4.

      When transferring to the PC, this option deletes the specified file on the PC (if it exists) and a new file is created.

    • Renames the file being transferred if a file of the same name already exists. The last three characters of the filename are changed to 001. If such a file already exists, the filename is changed to 002, and so on up to 999.
    • If the destination file exists, Reflection assumes it is there as the result of an aborted download and resumes the file transfer from the point of interruption. This option is relevant only for Zmodem transfers.
    • The file is not transferred and no error is returned. This option is relevant only for WRQ/Reflection and Zmodem transfers.
    • Transfers the file only if the source file is newer than the destination file. This option is relevant only for WRQ/Reflection transfers.
    • Uses the IfFileExists option specified by the remote system. If the remote system doesn't specify a IfFileExists option, this option is equivalent to DestinationFileExistsOption.Cancel. This option is relevant only for Zmodem transfers.
    See Also

    Reference

    FileTransfer Object
    FileTransfer Members

    Send Feedback