I had read in a previous post that it was recomended to use the event ResourcesFetched to limit down the visible resources.  The potential problem is that this could be a performance issue loading all of the various resources. 

After looking through the source code for the WebScheduleInfo control I noticed how you check the Visible Resources Count when doing the Databind(). 

I figured that if I set the visible resources that I am interested in prior to doing the Databind check I should be able to only show out the resources I am intrested in instead of loading all the resources then limiting them inside the ResourcesFetched event.

What I would like to do is extend out the WebScheduleInfo then override the DataBind method so that I can add 1..n resources into the VisibleResources Collection then call the base DataBind mentod.  I used the following code below to do just that (hard coded a single param for now) then dropped the new user control onto the page in place of the WebScheduleInfo control.  From what I can tell this appears to work.

The only part that I am still wondering about is how the WebScheduleInfo control and the WebScheduleSqlClientProvider play together with regards to what I am trying to accomplish (performance minded).

public partial class WebScheduleInfoExt : WebScheduleInfo
    {
        public override void DataBind()
        {
            Resource o1 = new Resource();
            o1.Key = "1";
            o1.Name = "Darren Straube";
            this.VisibleResources.Add(o1);
            base.DataBind();
        }
    }