Bug found when updating a one-time scheduled subscription...

When you first create a data-driven sub and schedule it to run "one time" it
works fine. Later, however, if you edit it to try and re-run it, you run
into a problem if the subscription is set to run on a one-time basis only
again. You select "one time" as the schedule and set the time you want it to
fire off. However you can't enter a date. Instead of picking up today as
the default like it does when you first create the subscription, it keeps the
same date that you originally used when you first set it up. So if you are
editing a one-time scheduled subscription and you didn't create the
subscription that same day, the schedule you just created is already in the
past and thus never fires. You can confirm this by checking the "startdate"
field of the "schedule table". I tried working around it by updating the
table manually...
Update Schedule
Set StartDate = '2004-11-10 14:10'
Where ScheduleID = 'whatever'
... but it still didn't fire off the job. Anyone else seen this?
sebring1130you can use the soap api and call rs.firevent on it
"sebring1130" wrote:
> When you first create a data-driven sub and schedule it to run "one time" it
> works fine. Later, however, if you edit it to try and re-run it, you run
> into a problem if the subscription is set to run on a one-time basis only
> again. You select "one time" as the schedule and set the time you want it to
> fire off. However you can't enter a date. Instead of picking up today as
> the default like it does when you first create the subscription, it keeps the
> same date that you originally used when you first set it up. So if you are
> editing a one-time scheduled subscription and you didn't create the
> subscription that same day, the schedule you just created is already in the
> past and thus never fires. You can confirm this by checking the "startdate"
> field of the "schedule table". I tried working around it by updating the
> table manually...
> Update Schedule
> Set StartDate = '2004-11-10 14:10'
> Where ScheduleID = 'whatever'
> ... but it still didn't fire off the job. Anyone else seen this?
> sebring1130
>
>