Hi Ben, glad to see you here. Welcome to our community forum.

Andi has pointed to the right direction. That's true, with over 18x more controls than its predecessor, maintaining the same price is truly a challenge for us.

Our goal is that all Silverlight and WPF developers can enjoy more streamlined RIA development using finest UI controls with full MVVM support, standards-compliance UX and also full design-time support -- and still well affordable within their budgets. 

That said, if you buy Silverlight subscription, you actually get around 120 controls, that's for both SL3 and SL4. In addition, another 60 WPF controls will be inserted to your account -- free of charge -- giving you a total of 180 controls in your toolbox.

Hopefully this is clear enough.

Regards,
Jimmy.

Hi Siva,

Yes, you can set ChildNotExpandable property to true. This property is available in WebGridRow class.

You can set the property in WebGrid1_InitializeRow event, which is shown in the following example. 

protected void WebGrid1_InitializeRow(object sender, ISNet.WebUI.WebGrid.RowEventArgs e)
    {
        if (e.Row.GetChildTableRows(e.Row.Table.ChildTables[0]).Count == 0)
            e.Row.ChildNotExpandable = true;
    }

Adding to Gordon's reply, the reason why we don't automate this process is for performance reason. The checking for each child table row could be expensive and developers often used different way to measure the child rows availability.

The above example will work if you're not using "hierarchical load on demand" feature, and it also assumes you're using strongly dataset which prefill the child rows, which may not be the case in some enterprise scenarios.

Thus, a better solution is to let customers decide their own way to measure the child rows availability, and set the property when necessary.

For instance, if you're using custom business object or LINQ query, you may use your own function such as:

if (!MyDAL.HasOrder(e.Row.KeyValue))
{
      e.Row.ChildNotExpandable = true;
}

Regards,
Jimmy.