I have avoided spaces in paths for PTC products for a while,
particularly on Windows systems. I do not know how Wildfire has
improved but Pro/I 3.3 and Pro/E 2001 still have some behind the scenes
issues with spaces in one way or another. Why bother fighting it?
Even Microsoft Outlook and other applications have to be told something
special to make spaces work for various reasons, such as typing a URL or
UNC path in an e-mail. If you want a space in it, you have to surround
it in "<>" to make it work. As someone else mentioned, you have to put
paths in double quotes for other Windows programs and for command-line
stuff.
Here's another odd thing spaces can do to you. A while before I started
work here, IT changed user names to First Last (with the space). Now
users here can't launch an object directly into Pro/E from a Workspace
(Pro/E 2001 and Pro/I 3.3). Things are also set up here to create a
user's Pro/I local database using the same username format in the path.
That keeps any program from opening an object from within a Workspace.
By removing that space in the path, users who need to update Word or
Excel documents here can now do so directly in the Workspace and save
back to the WS. Even with this change, a space in the username still
prevents Pro/E from working though. Yes, users can launch an object
with any application they want directly from a WS except for Pro/E.
Spaces are always going to be a problem somewhere because a space is
frequently an indicator of a separation between a command and an
argument or option. PTC can't fix this any more than Microsoft can.
Spaces have been possible in Unix a lot longer than in Windows but in
that "world" spaces in paths are still avoided.
