Hi Marc,
You can bind the SelectedValue property of a ComboBox, and any other property for that matter, to a data source on the Form using
the Properties window in VS.NET 2005. What exactly are you having trouble with?
The common properties are marked with BindableAttribute(true) in code so they appear in the Properties window under the Data
category and the "(DataBindings)" heading. You can click the ellipses button next to "(Advanced)" to view the remaining properties
of the Control to which you are binding.

Signature
Dave Sexton
> Hi,
>
[quoted text clipped - 22 lines]
> why doesn't the "bindingsource - field" syntax work for all
> properties?
Marc Vangrieken - 11 Aug 2006 10:43 GMT
Hi,
That's correct indeed; the problem was that my bindingssource was not
connected to any datasource in design-time, so it doesn't show up in
the pick list. I wanted to connect the bindingsource to a dataset in
runtime, but I didn't want to bind all the controls to the
bindingsource by code.
Then I tried to edit the properties manually (not using the pick list),
and it was possible to manually set a binding (via the properties
windows) by typing "BindingSource - Field". In the generated code, code
was added for the binding. This only was possible for the common
properties (BindableAttribute(true)), not for the other ones (because
you can't manually edit the "binding comboxbox" in that screen.
So I just wondered if this way of working is supported or not, also
because if did not find any information on it... Although I know the
drawbacks of this approach, I find myself wanting to do it in simple
cases.
Today i figured out how to do it for all properties, first add a
dataset in design time, connect to the bindingsource, bind all the
properties you want and then remove the dataset again, but leave the
bindingsources.
So actually, the "problem" is solved, but thanks anyway.
> Hi Marc,
>
[quoted text clipped - 34 lines]
> > why doesn't the "bindingsource - field" syntax work for all
> > properties?