Re: Unable opening a file, when filename + path are very long

Spaces are not your issue. Excess total path length is.

"Trilix" <Trilix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE8E7293-2E7A-4C00-ABB4-92EE95835698@xxxxxxxxxxxxxxxx
Hi,

We encountered a problem that we couldn't open a specific file on our
fileserver (win2000).

After I renamed the filename to something shorter, it worked. When I
renamed it back to the original length, the problem came back.

I assume this has something to do with a bad namingpolicy an more specific
with the number of spaces used. Just to give you an idea how long the
filename & path is :

Path = L:\Functions\FA\Financial Accounting\General\Rapportering
intern\Rapp
Dusseldorf\Actueel\rapp month QTR\rapdudo2007\1qtr 2007\December 2006

Filename = HFM Monthly Financial Statement Upload Template PER 01 2007
Belgium-1steversie.xls

As you can see. Very long with many spaces. Am I correct that the number
of spaces are the bad guys or is it just too long? What is the best
namingpolicy to use?

Thanks,
Jurgen



.

Relevant Pages

  • Re: Unable opening a file, when filename + path are very long
    ... The only thing to avoid this is, teach your users to save the content in the file and not in the name of the file. ... But still with shorter names you came in trouble, ... After I renamed the filename to something shorter, ... I assume this has something to do with a bad namingpolicy an more ...
    (microsoft.public.win2000.security)
  • Re: Encoding of file names
    ... system, stored on a Sun OS 5.8 fileserver, through a samba-mapped drive ... When I ask for an os.listdirof a relevant directory, ... whether the filename is valid, ... so look for ntpath.py in the Python lib folder.) ...
    (comp.lang.python)