MS Project 2003 server / MS Project 2003

[MS Project shut off while saving....]

Hello!

We are experiencing a problem here.
One of the user try to save a project of 1700 tasks get kicked out and
closes the MSP2003.
This is what she did...
1) Cut more than 10 tasks and paste to other summary tasks
2) click save
3) takes sometime and closes the MSP client.

Do someone know what causing this problem?

Any help is Greatly appreciated!

Sankar,PMP

 

[Gary L. Chefetz \(MVP\)]

Never use cut and paste on entire task rows, this duplicates more
information than you want, including database keys. This can cause fatal
plan corruption or more mild symptoms such as those you've experienced.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-
"MS Project shut off while saving...." <MS Project shut off while saving....
@discussions.microsoft.com> wrote in message
news:[email protected]...

 

[pajamasam]

Hi Gary,

Just read your remark and would like some clarification if possible. I am a
culprit of cutting/pasting tasks as well. So your recommendation for moving
tasks is to drag them to their new location? The only downside to this is if
their new location is a few hundred rows up or down. But, if this will
minimize possible file corruption, it's worth it. Thanks.

mark

 

[Gary L. Chefetz [MVP]]

What requires clarification? Don't cut and paste task rows if you're using
Project Server. It's probably a good idea not to do it with plain old
Project. If moving a task 200 rows is a bigger pain than recreating it
manually, then don't move it. However, if the task is started, move is the
only reasonable way. Maybe you can collapse some work paths in-between to
make the journey shorter.

 

[pajamasam]

Thanks for the reply Gary. I'll be more cautious with my future edits.

-Mark