risks "assign to" shows double-up list of users in lookup list

R

Rob Schneider

I'm messing around with Project Server 2003, Web Access, etc. using the
Sample database provided with the product. When in web access I create
a new Risk (or Issue), and I use the pull-down for the "assign to" and
"owner" I see all users' doubled-up, e.g. Jo Brown, Scot Bishop, Steve
Masters, etc. While the names are the same, Project seems them as
different users because if I pick the "wrong" one for say Jo Brown, then
when logged in as Jo Brown I want to see "my risks", I don't see the
ones assigned to the "other" Joe Brown.

I hope this explanation makes sense.

Where is the doubled up list controlled? I don't see double entries in
the user list in Project. All these sample users have single user ID's
in the Windows Server user list ... I'm stumped.

thanks,
rms
 
G

Gary L. Chefetz [MVP]

Rob:

You shouldn't be seeing "doubled up" anything. Could you be more specific?
Have you created local resources in your plan?
 
G

Gary L. Chefetz [MVP]

Rob:

I wish I had an explanation for you, but I don't. As I have the same sample
database and don't see the issue in my instance, I have to assume that this
was caused by something you did along the way. I'd need to look into the
database to get more clues. I'd like to isolate the events that led up to
it, simply so we can raise a bug issue if necessary or a flag of caution to
others.
 
R

Rob Schneider

I have confirmed that here is only one Windows ID for each of these
standard "test" database logins. I'm unable to find any source of
having double-names on these pull down list boxes....

rms
 
R

Rob Schneider

Gary,

I'm happy to dig deeper. Can you give me some pointers or things to look
at? I'll look at Sharepoint (per your other note). Any other thoughts
where to look in Sharepoint or elsewhere. With those pointers, I'll dig.

I guess for me the key is to identify the source of the pulldown list
box. This has to be a query somewhere against some table (and it
doesn't apparently ask for it to return unique records)...that's my much.

I can't think of anything I did that would cause this (famous last
words, of course).

Ski slopes with sons beakons shortly, so can get back to this after that
short break. but this important to me because I suspect a bug (but maybe
it's me), and it's for my personal learning.

Hope this is useful to you. Let us know.

rms
 
G

Gary L. Chefetz [MVP]

Rob:

I doubt this is happening in the Project Server database, and I've had
little time to explore the new SharePoint underpinnings. So, your guess is
as good as mine.
 
Top