Now you’ve done it. You created a number of tasks in Project 2007 using start dates that you entered manually. Or maybe someone handed you a schedule with many “Must Start On” constraints applied to tasks. Unless you have a good reason to use non-default constraints or manually entered dates on tasks, it is best to let project figure out the proper constraint and dates after you set up the relationship between tasks. Project will typically apply the “As Soon As Possible” (ASAP) constraint, for example, to tasks, because this constraint best reflects how most tasks are typically scheduled in the real world.
So how do you clean up a project with messy constraints and switch them back to Project’s preferred ASAP constraint? You could hunt for them one task at a time. But that’s too much work. Or you could add a Constraint Type column to a view, and search for them that way, but a bunch of work still remains. A better solution: search for the problem dates or constraints, and then have Project replace them automatically.
I told you that it seems a little backwards, but that’s how it goes sometimes in software.
Now, you don’t have to stop there. You can enter specific dates to look for in the Find what list, with a Test of “equals”, and replace those dates with an ASAP constraint.
"but that's how it goes sometimes in software" ?
This is supposed to be a product for sale. Of course, MS will tell you that this is what the majority of their customers wanted - "they listened to you" so they changed it that way just for them. Most of them couldn't boolean their biscuits out of a bag so they wanted the box to read from bottom to top, of course, LOL - when they put it the right way around they'll convince you that they fixed the program, just in time for release. baaa-aaa baa-aaa