All,

I come from the old days where filenames were always 8.3. I also used Unix very extensively.

Every fiber in my body says "Spaces in filenames are dangerous, even if it's OK to use some of the time."

Our organization is planning to implement a MS Project server for group-wise collaboration between us and our customers.

This means our office documents will go everywhere from SQL Server to IIS to FTP server, etc...

Recently, our Sales Director decided to standardize our filename naming convention, including a couple spaces in between the date and project name and customer name.

I promptly voiced a concern about having spaces in filenames, but my warnings are falling on deaf ears. I suspect I will be forced to "prove" my position soon.

I looked around for any good books, articles, or anything to help support my position, but really cannot find anything very credible.

I have 2 questions:

(1) Am I off base? Are we to the point today where we can safely assume "spaces in filenames" are never a problem?

(2) Am I on target? If I am on target, how do I "prove" my position effectively?

I look forward to thoughtful replies.

Thanks!

Dave