which global.mpt is used?

[Rob Schneider]

Folks,

I thought I had this sorted, but don't.

I have a set of project files and the associated global.mpt file stored
in a SharePoint server. I checkout to the local SharePoint drafts folder
the global.mpt, the shared resources.mpp fiel and all the *.mpp. I
launch Project 2007 with a special desktop icon with the "start-in"
folder defined to the local SharePoint drafts folder. This local
drafts folder is subfolder under "documents" in my profile (default
location).

On one computer (desktop), the "right" global.mpt file is picked up.
On antoehr computer (laptop), it picks up no global.mpt file.

I determine this by looking in the VB editor to see of the global.mpt
and the modules I want are recognised and they are not.

Any thoughts on why this is? I really thought if you lauch Project
with the "start-in" folder set, it looks there for global.mpt. Strangly
works on one computer and the other.

Driving me nuts... ideas?

 

[Rod Gill]

That has always worked for me. Can you make sure that on the PC it doesn't
work in that there are no spaces at the start or end of the string by
mistake? If the path has a space in it the whole path should be in double
quotes as in:

"C:\My projects"

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[Rob Schneider]

That has always worked for me. Can you make sure that on the PC it
doesn't work in that there are no spaces at the start or end of the
string by mistake? If the path has a space in it the whole path should
be in double quotes as in:

"C:\My projects"

Working on one PC and not the other was, in retrospect, a red herring.
Turns on that upon moving to the second pc (in the garden as the weather
was warm!), is when the error first showed up.

I think what has happened is that the global.mpt I was was using became
"corrupted". Instead of Project saying "I noticed you have a global.mpt
in the current directory and that you probably want to use it; but, it
is corrupted so I can't use it", it just doesn't load any global.mpt and
carries on; but things that depend on that global.mpt simple doesn't
work. Sigh

So, what I did is go back to all previous versions of the global.mpt to
find the most recent on that actually works. Caused some re-work; but
good news is I remembered the changes and had the old versions.

I don't know what caused the "corruption".