Move a task using the mouse.any way to keep it from scrolling to f

[Bud]

I do NOT want to use cut and paste. I want to use the mouse to move a task
that is up in my schedule to a location much further down. However when I use
the mouse and move it..... it moves way to fast a past my task I wish to move
it to.

Any way to move a task with the mouse feature and have the scroll go slower
or something.

Thanks

 

[Bud]

Can' use cut and paste because we have a system called Project Invision that
keeps track of tasks with IDs and also any actuals posted to that task.
So.....cutting the task esentially kind-of deletes and than syncronization
issues occur.

The only way we can do this here is to use the move with the mouse and it is
frustrating. I was hoping someone had a way to do this...............

 

[John]

Can' use cut and paste because we have a system called Project Invision that
keeps track of tasks with IDs and also any actuals posted to that task.
So.....cutting the task esentially kind-of deletes and than syncronization
issues occur.

The only way we can do this here is to use the move with the mouse and it is
frustrating. I was hoping someone had a way to do this...............

Bud,
Well, drag and drop is going to renumber the IDs the same as cut and
paste. If the add-on application, (i.e. Project Invision), you are using
is dependent on task ID, then you will be outta luck when it comes to
moving tasks around. I'm surprised a third party application tracks
project tasks by ID - generally the ID is a very poor indexing metric.

In plan development there may be reasons why you might need to move
tasks around but once a plan is being executed, it would be a VERY rare
case that would require tasks to be moved around. So what you are
requesting doesn't really make much sense - at least not to me. I must
be missing something.

By the way, just to be thorough, yes you can drag and drop tasks that
are "miles" apart in a large schedule without "scroll race".

John
Project MVP

 

[Bud]

Hi John

You replied.....By the way, just to be thorough, yes you can drag and drop
tasks that

are "miles" apart in a large schedule without "scroll race".

How can I do this without scroll race.....I just want to use the mouse and
move a task further in my schedule and do it so it doesn't scroll by
everything. Seems like I have little control as it races by everything.

Thanks

 

[John]

Hi John

You replied.....By the way, just to be thorough, yes you can drag and drop
tasks that

How can I do this without scroll race.....I just want to use the mouse and
move a task further in my schedule and do it so it doesn't scroll by
everything. Seems like I have little control as it races by everything.

Thanks

Bud,
I was hoping you might address the first two paragraphs of my response,
but, oh well.

To drag and drop more easily in a large file, designate a spare flag
field for the task(s) you want to move and the two tasks surrounding
where you want to drop them. Then filter on those flags. Now you can
easily drag and drop with no scrolling required.

John
Project MVP

 

[Bud]

Thanks!!

Sorry,........... here is brief answer to your paragraphs..........
What the third part application does is designates its own ID's per each
task and it keeps track of each task by this. If we cut and re-paste the task
from the schedule that is like a delete of the task pertheirID and a NEW add.
Let's say we had actuals recorded to that task. It keeps the OLD ID and task
in the database because it had actuals. Our timekeeping system is
separate(SAP) and it feeds PIV. In SAP or any other timekeeping system I am
familiar with it allows you to keep a template of your common tasks. If
someone kept that old task with that ID in their SAP template and recorded
some hours to it than it would try and post it. It is their but for all
intent and purpose it was deleted. So........we than get sync errors.

As for the moving around.........We are using a production support schedule
and the client area wants us to keep track of every Change request that we do
that is greater than a certain threshold like 20 hours. We can do hundreds of
these and when they are complete we like to move them down to the bottom of
the schedule in a completed area. There are many reasons we do this some of
which are its a better way to organize the data so we can see what is still
active in a better manner such as the Gantt chart and the resource usage
screen.

Hope that makes sense and Thanks Again!


Well, drag and drop is going to renumber the IDs the same as cut and

 

[Mike Glen]

Hi Bud,

Make sure you disable the autolink function in Tools/Options.../Schedule
tab!

FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials



.... We can do hundreds of

 

[John]

Thanks!!

Sorry,........... here is brief answer to your paragraphs..........
What the third part application does is designates its own ID's per each
task and it keeps track of each task by this. If we cut and re-paste the task
from the schedule that is like a delete of the task pertheirID and a NEW add.
Let's say we had actuals recorded to that task. It keeps the OLD ID and task
in the database because it had actuals. Our timekeeping system is
separate(SAP) and it feeds PIV. In SAP or any other timekeeping system I am
familiar with it allows you to keep a template of your common tasks. If
someone kept that old task with that ID in their SAP template and recorded
some hours to it than it would try and post it. It is their but for all
intent and purpose it was deleted. So........we than get sync errors.

As for the moving around.........We are using a production support schedule
and the client area wants us to keep track of every Change request that we do
that is greater than a certain threshold like 20 hours. We can do hundreds of
these and when they are complete we like to move them down to the bottom of
the schedule in a completed area. There are many reasons we do this some of
which are its a better way to organize the data so we can see what is still
active in a better manner such as the Gantt chart and the resource usage
screen.

Hope that makes sense and Thanks Again!

Bud,
Ok, thanks for the explanation. I now have a better understanding of
what appeared to be a dubious request. However it does appear you are
doing a lot of unnecessary file manipulation (more vulnerable to
screwing something up). Why not use filtering or grouping to single out
the current active data. That's what those features are there.

John
Project MVP

 

[Jim Spiller]

The Drag and Drop procedure preserves the Unique ID where the Cut and Paste
operation effectively deletes the task and adds it again thus creating a new
Unique ID. Your other application is most likely keying on Unique ID and if
so, you are correct in doing what you are doing to move tasks around. With
that said, there is no way to control the speed at which the screen scrolls
when you drag the mouse. Have you tried bumping (or tapping) the bottom of
the screen during the Drag operation. This moves the screen down a page or
so at a time. You can hold it there a little longer to go a few pages at a
time. I do this all the time and it works for me even on large projects.
Just don't let go of the mouse while you are doing this! And turn off
Autolink as was previously suggested.

 

[John]

The Drag and Drop procedure preserves the Unique ID where the Cut and Paste
operation effectively deletes the task and adds it again thus creating a new
Unique ID. Your other application is most likely keying on Unique ID and if
so, you are correct in doing what you are doing to move tasks around. With
that said, there is no way to control the speed at which the screen scrolls
when you drag the mouse. Have you tried bumping (or tapping) the bottom of
the screen during the Drag operation. This moves the screen down a page or
so at a time. You can hold it there a little longer to go a few pages at a
time. I do this all the time and it works for me even on large projects.
Just don't let go of the mouse while you are doing this! And turn off
Autolink as was previously suggested.

Jim,
After I replied, I realized that Bud must have been referring to the
Unique ID, not the normal ID field, so you are exactly right about the
difference between drag and drop and cut and paste - in both cases the
ID changes but the Unique ID is preserved with drag and drop.

I've tried the bump technique before and it's kind of like flying a
helicopter, you need a very light touch to keep it stable. The method I
suggested doesn't require fine motor skills although it will take a
little extra effort.

Another method I have used is to drag and drop in increments, (i.e. drop
to a temporary location within the same window view), but that can be
rather tedious and it's easy to screw up.

John
Project MVP