John
Fri Apr 20 11:45:42 CDT 2007
In article <5398D33E-0E3A-4CE9-ADEE-21D40104DEC9@microsoft.com>,
Pat <Pat@discussions.microsoft.com> wrote:
> John - that is exactly my problem. I was using cut & paste instead of drag &
> drop. Thanks for explaining how to do it!
> --
> Pat
Pat,
You're welcome and thanks for the feedback.
John
>
>
> "Dale Howard [MVP]" wrote:
>
> > John --
> >
> > Good point. Thanks for jumping into the thread with a few more ideas! :)
> >
> > --
> > Dale A. Howard [MVP]
> > VP of Educational Services
> > msProjectExperts
> >
http://www.msprojectexperts.com
> >
http://www.projectserverexperts.com
> > "We write the books on Project Server"
> >
> >
> > "John" <mjensen@theriver.com> wrote in message
> > news:mjensen-93B6D2.18455518042007@msnews.microsoft.com...
> > > In article <9A06120E-C0AB-4D2F-A2B4-D657588135F1@microsoft.com>,
> > > Pat <Pat@discussions.microsoft.com> wrote:
> > >
> > >> I would like to keep the unique id's the same, but is there a way to keep
> > >> from losing the unique id's while moving tasks around in the schedule?
> > >> Thanks!
> > >
> > > Pat,
> > > Just a clarification. Dale explained about the Unique ID but I wonder if
> > > perhaps you are moving tasks using cut and paste. In that case, the
> > > Unique ID will get reassigned, because the pasted task is in fact a new
> > > task. A better way to move tasks within a schedule is with drag and
> > > drop. To drag and drop first select the entire task row by clicking on
> > > the leftmost column (usually this is the ID field). Once the row is
> > > selected click and hold the ID field and drag it to where you want it.
> > > Release the mouse button. The ID will change to describe the new task
> > > sequencing but the Unique ID will stay with the moved task.
> > >
> > > John
> > > Project MVP
> >
> >
> >
> >