Changing Start Date affects Duration and/or Work in 2007 (not in 2003)
in [Project]
|
From: Luc Overdulve on 16 Feb 2010 12:06 I've searched all over for this strange behavior but I cannot find anything about it... In my plan there are only Tasks with Type=Fixed Duration and Effort Driven=No. Some Tasks have one of more Resources (type=Work) connected with Calendar=Project Calendar. One of the earliest tasks, planned to be started back in January will probably start now next week (from 22nd Feb), so while updating the plan I have to change that Start Date and after that all FS connected tasks will start at least as many days later as the duration of the changed task. When doing this in Project 2003 this works fine. In Project 2007 however there happens so much more! Many tasks now have a changed Duration too and/or the amount of Work is changed. I don't understand why this is happening (only) in Project 2007. Because I did not succeed in finding more about this on the world wide web of this group, I decided to post this question in here! Thanks a lot for any suggestion(s)! Luc (NL)
From: Rod Gill on 16 Feb 2010 16:11 Firstly, immediately download Service Pack 2 for Project and install, then try again. What you are experiencing should not happen and may indicate a file corruption. Does this happen in other files? If you save as .xml file type, close the project then re-open from the xml file, does the problem go away? (Only test this after updating to SP2). -- Rod Gill Microsoft MVP for Project - http://www.project-systems.co.nz Author of the only book on Project VBA, see: http://www.projectvbabook.com "Luc Overdulve" <l.overdulve(a)gw.rotterdam.nl> wrote in message news:8036b927-1032-46ca-8636-dbbf623184a9(a)f15g2000yqe.googlegroups.com... > I've searched all over for this strange behavior but I cannot find > anything about it... > > In my plan there are only Tasks with Type=Fixed Duration and Effort > Driven=No. > Some Tasks have one of more Resources (type=Work) connected with > Calendar=Project Calendar. > > One of the earliest tasks, planned to be started back in January will > probably start now next week (from 22nd Feb), so while updating the > plan I have to change that Start Date and after that all FS connected > tasks will start at least as many days later as the duration of the > changed task. When doing this in Project 2003 this works fine. > > In Project 2007 however there happens so much more! Many tasks now > have a changed Duration too and/or the amount of Work is changed. I > don't understand why this is happening (only) in Project 2007. > > Because I did not succeed in finding more about this on the world wide > web of this group, I decided to post this question in here! > > Thanks a lot for any suggestion(s)! > > Luc (NL) > > __________ Information from ESET Smart Security, version of virus > signature database 4872 (20100216) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > __________ Information from ESET Smart Security, version of virus signature database 4872 (20100216) __________ The message was checked by ESET Smart Security. http://www.eset.com
From: Luc Overdulve on 17 Feb 2010 08:57 Many thanks for your reply, Rod! First of all: we have SP2 already installed, but... Project is the only 2007 application, while all other MSO apps are XP (SP3). I 've found many tasks with SNET constraints inserted in this plan. When changing these constaints into ASAP (only if predecessor(s) available) just ONE task's Work/Cost changed; this task had a SNLT constraint. Then I followed your advise saving as XML and re-opening it as new project file. I am sorry I have to tell that the same issues appear when changing the Start date of this very task. Updating the plan had very high priority. So, I'll do this using Project 2003 for this moment. Later on I will try changing the same Start Date by changing the dependency's lag rather than by setting a SNET constraint; may be this will make sence? Any other suggestions? Luc (NL) On 16 feb, 22:11, "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote: > Firstly, immediately download Service Pack 2 for Project and install, then > try again. What you are experiencing should not happen and may indicate a > file corruption. Does this happen in other files? > > If you save as .xml file type, close the project then re-open from the xml > file, does the problem go away? (Only test this after updating to SP2). > > -- > > Rod Gill > Microsoft MVP for Project -http://www.project-systems.co.nz
From: Rod Gill on 17 Feb 2010 14:18 Maybe this task only is corrupt, so how about trying to delete it, then recreate? Certainly it is better practice to set lags to realistic values than edit dates. -- Rod Gill Microsoft MVP for Project - http://www.project-systems.co.nz Author of the only book on Project VBA, see: http://www.projectvbabook.com "Luc Overdulve" <l.overdulve(a)gw.rotterdam.nl> wrote in message news:f15d8c9e-e04d-4550-90f5-2c8f8ebadeb6(a)o3g2000yqb.googlegroups.com... > Many thanks for your reply, Rod! > > First of all: we have SP2 already installed, but... Project is the > only 2007 application, while all other MSO apps are XP (SP3). > > I 've found many tasks with SNET constraints inserted in this plan. > When changing these constaints into ASAP (only if predecessor(s) > available) just ONE task's Work/Cost changed; this task had a SNLT > constraint. > > Then I followed your advise saving as XML and re-opening it as new > project file. > I am sorry I have to tell that the same issues appear when changing > the Start date of this very task. > > Updating the plan had very high priority. So, I'll do this using > Project 2003 for this moment. > Later on I will try changing the same Start Date by changing the > dependency's lag rather than by setting a SNET constraint; may be this > will make sence? > > Any other suggestions? > > Luc (NL) > > > > On 16 feb, 22:11, "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote: >> Firstly, immediately download Service Pack 2 for Project and install, >> then >> try again. What you are experiencing should not happen and may indicate a >> file corruption. Does this happen in other files? >> >> If you save as .xml file type, close the project then re-open from the >> xml >> file, does the problem go away? (Only test this after updating to SP2). >> >> -- >> >> Rod Gill >> Microsoft MVP for Project -http://www.project-systems.co.nz > > __________ Information from ESET Smart Security, version of virus > signature database 4875 (20100217) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > __________ Information from ESET Smart Security, version of virus signature database 4875 (20100217) __________ The message was checked by ESET Smart Security. http://www.eset.com
From: Luc Overdulve on 18 Feb 2010 07:44
I have tried... Also replacement of tasks does not make sense here. I still wonder the different Service Packs (Project 2007 with SP2 MSO and Office XP with SP3) could be a conflicting cause of strange behaviors? It feels like seeing UFO's while there aren't... Luc (NL) |