CopyFile using - long file names

[BlackWisdom]

Hey Guys look at this code:



Let>filename=MergeSessionIncomplete
Let>newfilename=MergeSessionIncomplete.exe

CopyFile>filename,newfilename

I think Mach Sched does not like the format of my long filenames, when I run the above code the file generated look like this:

MergeSes

any ideas how to get around this...???

[Marcus Tettmar]

Hi,

There is no length limit. That works perfectly for me. Here's my script:


Let>path=C:\Documents and Settings\Marcus\My Documents\
Let>filename=%path%MergeSessionIncomplete
Let>newfilename=%path%MergeSessionIncomplete.exe
CopyFile>filename,newfilename


I made a small file called MergeSessionIncomplete and after running the script there exists MergeSessionIncomplete.exe

No issues. Which version of Macro Scheduler are you using and which version of Windows are you running?

[BlackWisdom]

thanks for the quick reply im running MSChed 7.3.11.4 with win 2k

but I noticed you did it slightly different from me - The program Im developing must allow the command to run from the root of the folder without any path given because I dont know where the user will install the app. But I got around it by using this code:


Let>filename=MergeSessionIncomplete
Let>newfilename=MergeSessionIncomplete.exe

CopyFile>filename,newfilename
MoveFile>MergeSes, MergeSessionIncomplete.exe

its somewhat sloppy, but it works...

[JRL]

Did some testing and found that BlackWisdom seems to be correct, the path added to the front of the file names causes CopyFile to function correctly when copying files in the current working directory. Additionally, if you add anything to the front of the destination file name CopyFile works correctly.

Try this, it works correctly:

Let>filename=MergeSessionIncomplete
Let>newfilename=AddMergeSessionIncomplete.exe

CopyFile>filename,newfilename

BlackWisdom,
I would recommend that you make a small change to your program and make the CopyFile destination name something completely different from "MergeSessionIncomplete". You are currently relying on the failure of the CopyFile program. If this turns out to be a Macro Scheduler problem and is fixed, the MoveFile operation will cause a failure notice on any WinNT 4.0 machine since the file "MergeSe" will not have been created.

Hope this is helpful,
Dick

[support]

but I noticed you did it slightly different from me - The program Im developing must allow the command to run from the root of the folder without any path given because I dont know where the user will install the app. But I got around it by using this code:

I don't see how this would work on the root though. This simply works on the current directory since you have specified no drive or path. It will not necessarily work at the root level unless that is the current directory.