D
Denis in Brisbane
In chasing another problem I've been advised that I should avoid using
hyphens in projects names, task names, resource names, enterprise codes and
enterprise outline codes.
That seems to be unreasonably restrictive. This package is supposed to be
used by senior execs who'll see project names with underscores and think it's
computer talk, not English. It often makes sense to use hyphens in task
names. eg: "Phase 1 - Initiation". On top of which, some people actually
have hyphenated names.
I can't find any mention of it in Microsoft doco. If it's actually the
case, I'd like to understand why it's the case. Can anybody shed any light
on it?
If it's real I'd consider it a bug and request that Microsoft fix it.
Denis
hyphens in projects names, task names, resource names, enterprise codes and
enterprise outline codes.
That seems to be unreasonably restrictive. This package is supposed to be
used by senior execs who'll see project names with underscores and think it's
computer talk, not English. It often makes sense to use hyphens in task
names. eg: "Phase 1 - Initiation". On top of which, some people actually
have hyphenated names.
I can't find any mention of it in Microsoft doco. If it's actually the
case, I'd like to understand why it's the case. Can anybody shed any light
on it?
If it's real I'd consider it a bug and request that Microsoft fix it.
Denis