>Jamie,
>
>I don't know the best answer, but my gut instinct is that you're better off creating these specialized methods and even tables to support your scheduling function. Scheduling takes complex algorithms, that may result in extra methods and extra tables, no way around it. Then, after you develop these new methods you may decide you need something different to meet your scheduling requirements. It will be a learning process for you.
>
>Wally

I guess that you've handled scheduling before. It's fun isn't it !! :)
Lots of meta-data and number crunching.

I was wondering whether the different facets of scheduling eg. Scheduling jobs, Reporting on schedules for certain day,Allowing users to modify parameters etc. etc. should be all withing the one businesss object or split up into several.

Cheers,
Jamie