Solved fileCopy error

[conception_native_0123]

do not know if this has been answered before but i found this one

path not found in filecopy-VBForums

Im wondering whats wrong with my code Since C:\Manual.txt is my source file and C:\Documents and Settings\Cedrich Lord\My Documents\Bluetooth Exchange Folder\ is the destination folder FileCopy "C:\Manual.txt", "C:\Documents and Settings\Cedrich Lord\My Documents\Bluetooth Exchange...

www.vbforums.com

but it not quantify my issue. i am running test code to copy text files from one directory to other. i keep getting path not found error. but source file exists. what i doing wrong? thank you. here is my code

Public Sub copyTXTs()
On Error Resume Next
Dim sFile As String
Dim tFile As String
Const dirSource As String = "C:\finance\"
Const dirTarget As String = "C:\finance\new\"
sFile = "celtic.txt"
tFile = "celtic.txt"
  FileCopy dirSource & sFile, dirTarget & tFile
Exit Sub

 

[arnelgp]

you need to check if folder "new" already exists.

 

[Minty]

Does the new folder already exist?

 

[arnelgp]

you can create a function that will "force" create the "new" folder.
and call the function first before copying:

public function fnForceMKDir(byval sPath as string) as string
dim i as integer, v as variant, s as string
fnForceMKDir = sPath
v = split(spath, "\")
on error resume next
for i = 0 to ubound(v)
s = s & v(i)
vba.mkdir s
s = s & "\"
next
end function

 

[conception_native_0123]

Does the new folder already exist?

yes guys it already exists. dont know what is wrong.

 

[conception_native_0123]

i even started and restarted the program many times. so memory should be destroyed many times too.

 

[Minty]

Remove the On Error Resume Next - you need to see where the error is occurring.

 

[conception_native_0123]

I did and it is occurring on the only line that says file copy

 

[conception_native_0123]

Beside I have programs set to break all errors anyway

 

[The_Doc_Man]

I have occasionally had issues with using constants in the way you are using them. Change your code to look like this:

Public Sub copyTXTs()
On Error Resume Next
Dim sFile As String
Dim tFile As String
Const dirSource As String = "C:\finance\"
Const dirTarget As String = "C:\finance\new\"
sFile = dirSource & "celtic.txt"       'concatenate directory to file
tFile = dirTarget & "celtic.txt"        'concatenate directory to file
  FileCopy  sFile,  tFile                 ' use concatenated strings to do the work
Exit Sub

If this fixes it, great! If not, then I don't see another obvious source of errors here. But string constants are sometimes odd in their behavior and I never figured out why.

 

[Minty]

Having error handling active when you are developing, and particularly when debugging is really unhelpful, as it often hides an issue.

There is nothing obviously wrong with your code other than the strange use of the Const for the target path strings.

 

[conception_native_0123]

Public Sub copyTXTs()
On Error Resume Next
Dim sFile As String
Dim tFile As String
Const dirSource As String = "C:\finance\"
Const dirTarget As String = "C:\finance\new\"
sFile = dirSource & "celtic.txt"       'concatenate directory to file
tFile = dirTarget & "celtic.txt"        'concatenate directory to file
  FileCopy  sFile,  tFile                 ' use concatenated strings to do the work
Exit Sub

that did trick! i do not know why it was an error. thank you doc man and everyone elsee. problem solved!

 

[The_Doc_Man]

Great. I have no specifics about why they don't work right, but CONST strings just don't act like ordinary variables. For example,

VBA: Global Constant Strings

I'm working with special characters for mathematics in Excel. (Exponents⁴, GRΣΣK, and other misc Unicode characters.) I'd like to store commonly-used Unicode strings as global constants, since that

stackoverflow.com

According to the person who filed this report, the strings act as though they are empty strings when referenced as though they were variables. If that is what was happening to you, then that would certainly explain what you say.

It PROBABLY has to do with the fact that the constant strings are not declared in the same memory area as ordinary DIM, PUBLIC, or PRIVATE variables. They are defined at compile time and are the same as other literal constants - stored in an area where modification is not allowed.

 

[conception_native_0123]

According to the person who filed this report, the strings act as though they are empty strings when referenced as though they were variables.

yes but CAN they be referenced as variables? as in, USED as variables? I always use them this way

 

[Minty]

I'm guessing that the clue is in the name, they aren't variables - they are Constants.

In your code example, there is no reason at all to declare them as a constant, they are only used in this module and not referenced by anything else. I Use a Const for things like a default SQL String used in a forms rowsource, and set them up on the top of a form module.

I agree there seems no obvious cause that they should fail, but they did.

 

[The_Doc_Man]

yes but CAN they be referenced as variables? as in, USED as variables? I always use them this way

The specific question is whether they can be used as actual arguments in sub/function usage. Obviously, in the modification I suggested to you, they are indeed used as variables and they work great, as you reported. But in the case where the constants appeared in the line of the FileCopy, I'm not sure what is going on there.