View Single Post
  #2 (permalink)  
Old September 15th, 2006, 09:59 AM
BrianWren BrianWren is offline
Friend of Wrox
 
Join Date: Nov 2004
Location: Port Orchard, WA, USA.
Posts: 1,621
Thanks: 1
Thanked 3 Times in 3 Posts
Default

Before you invoke this line of code that is raising the error you need to evaluate the path string and make a program flow branch in response to what you find.

Obviously, you have names in your system which are longer than Microsoft anticipated. (I'm on Microsoft's side here—there is no good reason for such lengthy paths. Path names are not meant to be commentary.)

If this is under your control, come up with a way to use shorter paths that still give the necessary isolation of file groups. If it is not under your control you can still make recommendations.

If the path is too long, it is too long. Perhaps you can temporarily create a mapped drive to symbolize a longer path (C:\ThisIsMyLocationForMostOfMySeldomUsedFilesAndO therWork\Ones_I_ReallyNeverUse\ can be turned into T:\). There is a possibility that even mapped drives are turned into fully-qualified paths when they are resolved however. Some experimentation would clarify whether that is so or not.
Reply With Quote