wsh(Windows Scripting Host), Long Path Names give Runtime error 76

Long Path Names give Runtime error 76 - Path not found

Author	Message
Eric Westro #1 / 3	Long Path Names give Runtime error 76 - Path not found I am writing a script which will move files to a holding directory while keeping the same base path intact. I have run into a quirk where the script will work correctly on 80% of the files and on the other 20% I get a run-time error 76 (path not found) when I attempt to move the file. I am using the FSO.Move method and the target is usually a long path/file name when I encounter this error. In addition, the destination directory has already been created before the Move is initiated. Does anyone know of any issue regarding long path/filenames being passed to the FSO methods via a variable? Here is a sample from the script: 'Note: sFile is a FSO destPath = HoldPath & Right(sFile.Path, len(sFile.Path)-2) sFile.Move destPath Thanks for the Help - Eric
Sat, 12 Oct 2002 03:00:00 GMT

Bill Purse #2 / 3	Long Path Names give Runtime error 76 - Path not found I've encountered a problem that appears to be related to NTFS formatted drives where the script is getting short file names instead of long ones. I haven't figured out what the work-around is yet. Possibly yours is a similar problem. Quote: > I am writing a script which will move files to a holding directory while > keeping the same base path intact. I have run into a quirk where the script > will work correctly on 80% of the files and on the other 20% I get a > run-time error 76 (path not found) when I attempt to move the file. > I am using the FSO.Move method and the target is usually a long path/file > name when I encounter this error. In addition, the destination directory has > already been created before the Move is initiated. > Does anyone know of any issue regarding long path/filenames being passed to > the FSO methods via a variable? > Here is a sample from the script: > 'Note: sFile is a FSO > destPath = HoldPath & Right(sFile.Path, len(sFile.Path)-2) > sFile.Move destPath > Thanks for the Help > - Eric
Sat, 12 Oct 2002 03:00:00 GMT

Eric Westro #3 / 3	Long Path Names give Runtime error 76 - Path not found I don't think this is the case with my problem. I inserted debug code and determined that the script is getting the proper file/pathname into the variable. I think there may be an issue with the FSO.move method. - Eric Quote: > I've encountered a problem that appears to be related to NTFS formatted > drives where the script is getting short file names instead of long ones. I > haven't figured out what the work-around is yet. Possibly yours is a > similar problem. > > I am writing a script which will move files to a holding directory while > > keeping the same base path intact. I have run into a quirk where the > script > > will work correctly on 80% of the files and on the other 20% I get a > > run-time error 76 (path not found) when I attempt to move the file. > > I am using the FSO.Move method and the target is usually a long path/file > > name when I encounter this error. In addition, the destination directory > has > > already been created before the Move is initiated. > > Does anyone know of any issue regarding long path/filenames being passed > to > > the FSO methods via a variable? > > Here is a sample from the script: > > 'Note: sFile is a FSO > > destPath = HoldPath & Right(sFile.Path, len(sFile.Path)-2) > > sFile.Move destPath > > Thanks for the Help > > - Eric
Sun, 13 Oct 2002 03:00:00 GMT

Page 1 of 1

[ 3 post ]