A
ann
Thanks a lot for your response..
Here's what we actually do each week-
We make changes to the schedule through the week. At the end of the
week, we submit this schedule to the time office to reflect the time
entries/actuals. So beginning the next week, we need to refresh the
published version with this updated copy that we receive fromt them.
I don't think getting to delete the original version will be feasible
each week!
So based on what you are saying, then, we might have to get a work
around with our process...Isn't it? Any other suggestions?
Thank you!
Post a follow-up to this message
Message 2 in thread
From: Dale Howard [MVP] (dale(dot)howard(at)msprojectexperts.com)
Subject: Re: Overwriting published projects
View this article only
Newsgroups: microsoft.public.project.pro_and_server
Date: 2004-12-08 13:28:57 PST
Ann --
You cannot promote an alternate Version of a project and make it the
Published version. The alternate versions are meant to be like
"snapshots"
of the project at a particular point in time. If you have an
alternate
Version that needs to become the Published version, then do the
following:
1. Open the alternate version of the project in Microsoft Project
Professional
2. Save the alternate version as an .mpp file
3. Ask your Project Server administrator to delete all versions of
the
project from the Project Server database
4. Import the alternate version into Project Server in Microsoft
Project
Professional using Tools - Enterprise Options - Import Project to
Enterprise
This will make the alternate version of the project the Published
version.
You should always make changes to your Published version as it is the
production version of your project, and then do File - Save As to save
alternate Versions. Hope this helps.
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
Denver, Colorado
http://www.msprojectexperts.com
"We wrote the book on Project Server"
Here's what we actually do each week-
We make changes to the schedule through the week. At the end of the
week, we submit this schedule to the time office to reflect the time
entries/actuals. So beginning the next week, we need to refresh the
published version with this updated copy that we receive fromt them.
I don't think getting to delete the original version will be feasible
each week!
So based on what you are saying, then, we might have to get a work
around with our process...Isn't it? Any other suggestions?
Thank you!
Post a follow-up to this message
Message 2 in thread
From: Dale Howard [MVP] (dale(dot)howard(at)msprojectexperts.com)
Subject: Re: Overwriting published projects
View this article only
Newsgroups: microsoft.public.project.pro_and_server
Date: 2004-12-08 13:28:57 PST
Ann --
You cannot promote an alternate Version of a project and make it the
Published version. The alternate versions are meant to be like
"snapshots"
of the project at a particular point in time. If you have an
alternate
Version that needs to become the Published version, then do the
following:
1. Open the alternate version of the project in Microsoft Project
Professional
2. Save the alternate version as an .mpp file
3. Ask your Project Server administrator to delete all versions of
the
project from the Project Server database
4. Import the alternate version into Project Server in Microsoft
Project
Professional using Tools - Enterprise Options - Import Project to
Enterprise
This will make the alternate version of the project the Published
version.
You should always make changes to your Published version as it is the
production version of your project, and then do File - Save As to save
alternate Versions. Hope this helps.
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
Denver, Colorado
http://www.msprojectexperts.com
"We wrote the book on Project Server"