Brad Hile [EMAIL PROTECTED] on 12/2/02 5:45 AM wrote: > > Colin you're brilliant! (fading memory or not)
*Blushing* Naaah, I just bumped into the same problem you have. > As to why I would possibly want a path over 126 chars? It's just a case of > better sure than sorry as the app I'm building will allow users to choose a > destination for their files to be saved. This is precisely what had happened to me a couple years back. I built an app that would automatically create a text file in a sub directory at the root of the app. When testing on Windows, some people placed the app in a relatively deep directory path. FileIO could create the text file well enough but could not open it (if the file path was longer than 126 characters). Now to add to this, I believe that other media types that use file paths have the same problem on windows machines. I have seen this for instance with QT cast members not being able to find the external QT file if the file path was longer than 126 characters. So this problem is not exclusive to fielIO. This is not a minor issue as any standalone director project you've created could potentially break if the user decides to put the app in a relatively deep directory (I say relatively because 126 characters is really not that deep of a file path). I know for a certainty that this will break fileIO openFile() and QT's and quite possibly other externally linked media types on windows machines. Take this as a cautionary warning. ck [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
