Projects with a Project Name containing a Comma cannot be Linked?

A

Ann

Hello All,

I am able to create and save a project file to project
server with a file name that contains a comma called "This
is a comma, test". However, when I try to create an
external predecessor in another project file by double-
clicking on the task, selecting the "Predecessors" tab,
and typing:

<>\This is a comma, test.Published\11

in the ID column I receive the following message:
"Invalid predecessor. Try one of the following:
*Type only positive, whole numbers.
*Type predecessor information in the following order:
predecessor ID number, dependency, and lead or lag time.
* If the preecessor information is too long, use the Task
Information dialog box."

I also created a file called "This is a comma test"
(WITHOUT a comma) with the exact same task information and
was able to create the external dependency using the above
procedure with " <>\This is a comma test.Published\11" as
the ID.

If you have any idea why this might be occuring, please
let me know. If anyone has experienced this in their
administration or usage of Project Professional 2002,
please let me know.

Thanks very much in advance,
Ann
 
S

Steve Kearon

the problem arises because the comma is also the list separator character on
your system. This causes MSProject to fail when splitting a field containing
the filename into its constituent parts: its interpreting your input as two
(comma separated) dependencies, both of which fail to be recognized.

MSProject will also be unable to consolidate projects with commas in their
filenames.

I can think of only two solutions: stop using commas in filenames or change
the system-wide list separator character (& then ensure you don't use
whatever character you chose in filenames). The former is probably best.

Hope this helps

Steve
 
Top