You might check out Brian Noyes' book on data binding.
He explains how to create your own components and support
data binding for them. I haven't done that, but made
a note where I could find the information if I needed it.

Robin S.
-----------------------------------------------

Hi,

If you wrote a Control then you would use the Control's BindingContext
property, if it hasn't been set it would get the parents one.

Yes the Container is seperated from the Form, and i don't think you can
access the Form from a Component at runtime.   Keep in mind that Component
could be used without a Form.

I did a quick google search and found something interesting, some code which
makes the designer write code to associate the Component with current
Form/UserControl.
http://groups.google.be/group/microsoft.public.dotnet.framework.windowsforms/bro
wse_thread/thread/9e44c3983e0e0c76/14ae6e6eb98cb7a0?lnk=st&q=%2B%22form+from+com
ponent&rnum=1&hl=nl#14ae6e6eb98cb7a0
(There was a typo, so i put working code at the bottom)

Having said this, i'm not quite sure if it's a good idea to assiociate a
Component with a Form or UserControl ... AFAIK non of the standard
Components do this.

You might also want to ask this question in a broader ng, like
dotnet.framework since it's not just a DataBinding problem.

HTH,
Greetings

public class SomeComponent : Component
{
private Control hostControl;

// ............

public Control HostControl
{
  get { return hostControl; }
  set { hostControl = value; }
}

public override ISite Site
{
get { return base.Site; }
set
{
  base.Site = value;
  IDesignerHost h =
(IDesignerHost)value.GetService(typeof(IDesignerHost) );
  this.HostControl = (Control)h.RootComponent;
 }
}
}