Need Guidance Using SharePoint and Microsoft Project Professional

[Marty72853]

Body I want to create an Integrated Master Schedule (IMS) by inserting the
individual MS Project files that reside on SharePoint 2007 within a Master
Project File that will also reside on SharePoint 2007.

The current situation is that I am working in an organization that is using
SharePoint 2007 and Microsoft Project Professional installed in a virtual
manner. I do not have Project Server and will not be getting it.

I am hoping that someone can tell me how to accomplish this within the
constraints of my current situation.

 

[Dale Howard [MVP]]

Marty72853 --

I do not believe there is any way to create a master project when the
subprojects are saved in SharePoint. Hope this helps.

 

[Rob Schneider]

Body I want to create an Integrated Master Schedule (IMS) by inserting the
individual MS Project files that reside on SharePoint 2007 within a Master
Project File that will also reside on SharePoint 2007.

The current situation is that I am working in an organization that is using
SharePoint 2007 and Microsoft Project Professional installed in a virtual
manner. I do not have Project Server and will not be getting it.

I am hoping that someone can tell me how to accomplish this within the
constraints of my current situation.

We are doing this right now. Store the subproject, master, and the
shared resource file (if you have one) in SharePoint. We also put the
customised global.mpt file that is applicable to this "set" of files
into SharePoint also.

When it comes time to update the files, simply check them out.
SharePoint will download the files (individual, master, and global) into
the local SharePoint folder.

Create yourself a desktop shortcut to launch Project by copying one that
you already have. Edit that shortcut to change the "start-in" folder to
the SharePoint local folder. THen launch Project. It will use the
global.mpt that it finds there. Open the master file. Insert all the
projects as links from the SharePoint local drafts folder. Linke the
"user shared resource file" fromthat local drafts folder. You can even
cross link across project files if you want.

When done, simply check back into SharePoint. Sharepoint will copy the
files from your local drafts folder to the SharepPoint doc library,
incrementing versions, and all that.

 

[Dale Howard [MVP]]

Rob --

Thanks for correcting me. So many users have had this problem that I
assumed it simply could not be done!

 

[Marty72853]

Rob,

I am still having a problem. I have checked out the files from SharePoint
(individual, master, and global) into the local SharePoint folder on my C
Drive.

I created a desktop shortcut to launch Project by copying one that I already
have. I edited that shortcut to change the "start-in" folder to the
SharePoint local folder which is on my C Drive.

Then I launch Project. Next I open the Master File. Insert all the projects
as links from the SharePoint local drafts folder. When done, I checked all
back into SharePoint. SharePoint copied the files from my local drafts folder
to the SharePoint doc library, incrementing versions, and all that.

The problem is when someone tries to open the Master File; the inserted
projects will not open because the reference is still to the local SharePoint
folder on my C Drive.

Any ideas? Or am I not doing something correctly?

 

[Rob Schneider]

Marty,

"Someone" need to do as you do ... Setup Project to start in the correct
"local drafts folder", check out, launch Project, do their work, check
in the files.

SharePoint is the safe place (access control, version control, etc)
where the files are stored. Project and the local drafts folder is
where all the action is.

(I wish Project was sophisticated enough to link to a file defined by a
URL pointing to the SharePoint library, but it is not).

 

[Rob Schneider]

Rob --

Thanks for correcting me. So many users have had this problem that I
assumed it simply could not be done!

I can't explain why so many people are having problems. We done a lot of
integration between Project and SharePoint. Boggles the mind how
powerful yet simple the concept is.