Hi Gary,
Let me comment on this.
Who says nobody used custom fields (in Professional, I mean) on assignment
level? They are THE way to group to reply to questions like the poster's,
and that worked perfectly in 2002/2003.
So in Professional there is no such thing as "the addition of assignment
level custom fields" (that happened as far as I remember in 2000). Maybe
they couldn't be "customized" the same way as Task or Resource fields but
they could hold a value, ONE value for ONE assignment.
In these versions, the assignment object was well defined, and each property
of it had ONE value.
Now when today using the API you define an assignment object and you call
for the value of a custom field (same coding, ass.text1) you may get two
different values depending on how you define the assignment.
I do not think this is normal IT standard, any programmer producing such a
flaw would be punished severely..
And I fail to see the impact on server because in Server you name the cistom
fields and then they are disconnected from the standard ones like text1
altogether.
Sorry but this is really not "a feature".
Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf