scheduler remote management...

[Tiffers]

Hi,

I've been asked to make an instance of scheduler on a server manageable remotely, via the web.

This all seemed pretty straightforward, I made a simple ASP that updated a field in the schedule.mdb, and it was OK. Problem I hit is that scheduler doesn't notice the updated values until you restart it.
I contacted cognos and they said the API was the only way to interact with it, but said that access might have a better way and in fact weren't a great deal of use.
Writing values to a table from an ASP page and then scheduling a macro to update scheduler from those values seems a bit of a mental way to go about things...
Or, update the mdb anyway and just have a task that starts and stops it?

oo messy..

help!!

Tiff %-)

 

[DoubleD]

I'd have to look at the code for Scheduler.mdb, but my guess is you could requery the Scheduler form in Access and this would cause it to register the changes.

I don't see stopping and starting Scheduler as a big deal if you can limit it to once a day.

I am what I am based on the decisions I have made.

DoubleD

 

[drlex]

I'm with you, DoubleD.
Since it seems sensible to reboot a Windows server once a day (after backing it up), then any scheduler changes will kick in on restart.

soi la, soi carre

 

[Tiffers]

thanks guys

I'd have to look at the code for Scheduler.mdb, but my guess is you could requery the Scheduler form in Access and this would cause it to register the changes.

I'm not sure what you mean here?

The thing I was thinking with starting and stopping scheduler is that it will be updating the mdb when it runs tasks, and I don't know if it will overwrite the changes the ASP would have made. I suppose I'd better do a bit more testing.....