Clarity

Hi,

We use MS Project - Clarity Integration.
We recently upgraded from MS Project 2003 to MS Project 2010.

Some users are getting this error message when they try to open their schedule in MS Project 2010.

"Ambiguous name detected. :~ "

Has anyone encountered this and anybody how do I fix this?


Eddie.

Eddie -

What version of Clarity are you running? MSP 2010 isn't supported in Clarity 12.1. or earlier versions so I don't know if that might be an issue or not.

Ruthann

Sound like not unique.
Could it be that a role is twice in the project team which is support by Clarity but not by MS Project?.

Martti K.

Even I'm getting a similar error...

"Ambiguous name detected. : Project_Open "

I was experimenting on the usage of msp and tried to open clarity project.. I don't know what I have done exactly but this is what I'm getting after that.. :sad

Ritesh.

This looks like a MSP internal technical (VBA) error message to me. I think it happens when a function/procedure is defined twice. Try uninstalling the MSP interface and reinstalling it.

Thanks Gauri..

Sure, I'll try that..

Regards,
Ritesh

Hi Ritesh,

I'm receiving the same error.
Did you manage to fix this?

if so, what did you do?


thanks in advance,
Matt

Hi Matt,

Please try uninstalling and installing the interface. That solves several problems with the MSP.

BTW, the root cause for the error: The project was not closed properly (closing the MSP directly)

Thanks & Regards,
Ritesh Kumar

That root cause qualifies as a Tuesday's tip. Thanks
Also this thread is another lesson in how to read error messages:

"Ambiguous name detected. :~ "

When you have a project open there is a temporary file just like with MS Office docs.
The file name has that [size=5]~[size].

Many of the users of the schedulers are aware of that.
When you have a stand alone scheduler you you close it without closing the project you get similar error when you try to open the next time. Just delete the temporary file and you can open the project.

Martti K.

Thank you everyone.

A clean uninstall and reinstall of the MSP interface (I did the schedule connect too for good measure) seemed to sort out the problem.

Now need to work our custom VBA into the new global.mpt file.....


happy days..


Matt