There are some serious issues with javascript errors produced when using Peter Blum's DataPackage controls or Intersoft's WebCombo and WebGrid controls on a MM.NET webform. What happens is two-fold:

1) Each MM.NET webform has a FocusedControl property. If you fail to set this property (in other words, allow the default which is nothing), then the WebCombo or WebGrid controls from Intersoft generate a javascript error when you click on those controls. The error is: "Microsoft JScript runtime error: Object expected." If you set the FocusedControl property to some control on the form, the javascript error does not occur... the control works properly.

2) If you move or add controls to a webform after seting the FocusedControl property to some control, the webform "forgets" that this property has been set. Each time you make changes to the form, you have to make sure that the FocusedControl property is set. This is a sporadic problem. However, it does occur "several" times during the course of editing a webform.

3) If a business rule violation generates an error message, and PeterBlum's DatePackage control(s) are on the form, and you simply roll the cursor over the DateControl popup icon, a javascript error is generated: "Microsoft JScript runtime error: Object expected." Curiously, the Intersoft controls work fine.

These errors ONLY occur in the context of an MM.NET application. These controls work as expected in non-MM.NET webforms. I have built several applications in an attempt to debug this. The only conclusion I have been able to confirm is that the errors only occur on a MM.NET webform.