Is it possible to use the same lookup table for two different custom fields?

[anovak]

For example, the same structure is identical between a "Performer"
lookup and a "Customer" lookup in our case. Each performing group
could be a Customer (dept/grp) and vice versa.

Is this a "no-no" or is it "legal"?

Thanks,
Andy Novak
UNT

 

[Dale Howard [MVP]]

Andy --

This is absolutely A-OK to do. In fact, doing so saves a great deal of time
if you need to change any of the information in the Lookup Table, since you
need to change it only once, and it impacts both custom fields. Hope this
helps.

 

[anovak]

Andy --

This is absolutely A-OK to do. In fact, doing so saves a great deal of time
if you need to change any of the information in the Lookup Table, since you
need to change it only once, and it impacts both custom fields. Hope this
helps.

Well, I had already taken advantage of that the other day, but I've
had some hic-ups with some of the custom fields and was hoping sharing
the look up table wasn't causing the problem. Thank you ,sir.

 

[Dale Howard [MVP]]

Andy --

I suspect the hiccups are from publishing a project from within PWA, rather
than by using the Project Professional 2007 client. Hope this helps.

 

[Jack Dahlgren]

Dale,

Earlier this week we tracked down some issues to what appeared to be two
custom fields sharing the same look-up table. I can't be sure that was the
root cause, but when we got rid of those fields and implemented them with
individual look-up tables the problem disappeared.

I'd not be quick to try doing it again.

--
Jack Dahlgren
Project Blog: http://zo-d.com/blog
Macros: http://masamiki.com/project/macros.htm

 

[Dale Howard [MVP]]

Jack --

Thanks for sharing your pain. As buggy as Project Server 2007 is, who can
ever be sure of the root cause of anything anymore?