'next run date' isn't something you can set in the scheduling. The jobs are already scheduled and created. Going back through and rescheduling them all (if this would even reset the 'next run date') would be impractical. The answer for me is the reply above. Deleting and recreating the jobs with a sql script is quick and resets the 'next run date' to the current day and time of schedule. This is only a problem because I'm rolling the date backwards while doing my testing and this puts my 'next run date' a week in advance so my jobs never run.

Edited by - cyblue on 05/14/2003 4:31:06 PM