Long Path Names give Runtime error 76 - Path not found 
Author Message
 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  
 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  
 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  
 
 [ 3 post ] 

 Relevant Pages 

1. Long Path Names give Runtime error 76 - Path not found

2. Error 76 Path not found with folder object

3. 76 means to be "Path not found

4. Access97, Win95 Error 76 Path error 99

5. GetFolder gives me PATH not found

6. Mysterious path not found error 76 , caused by P&D? (vb6)

7. ADSI:GetObject network path not found reading info other than the current computer name

8. Runtime error 76 using Windows2000

9. amovie and runtime error 76

10. Runtime error 76

11. Runtime error 76?

12. Runtime error 76?

 

 
Powered by phpBB® Forum Software