WD98: Visual Basic for Applications Command for Copying Files (183868)

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. The following macro copies the file "My Document" from to the folder This example provides an error trap which alerts you when you need to take corrective steps to complete the operation.

   Sub FileCopyExample()
      Dim sSourcePath As String
      Dim sTargetPath As String

      ' Change these paths to your Source and Target paths.
      sSourcePath = "Macintosh HD:Documents:My Document"
      sTargetPath  = "Macintosh HD:Backup:"
      On Error Resume Next

      ' Copy the file "My Document" file from "Macintosh HD:Documents"
      ' to "Macintosh HD:Backup".
      FileCopy sSourcePath, sTargetPath

      If Err > 0 Then MsgBox Err.Description
   End Sub
				

NOTE: If you try to use the FileCopy statement on a file that is currently open, you receive a "Permission Denied" error.

Unlike the Wordbasic CopyFile command, if a file of the same name already exists in the target directory, Word will not display a message asking if you want to replace the existing file.

For more information about the FileCopy Statement, from the Visual Basic Editor, click the Office Assistant, type FileCopy, click Search, and then click to view "FileCopy Statement."

NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If the Assistant is not able to answer your query, please see the following article in the Microsoft Knowledge Base: For additional information, please see the following article in the Microsoft Knowledge Base: