Hi!
I put a BindingNavigator on a Form1 and set Modifier=Public. Then I created an inherited Form2.
I put a BindingSource on Form2. But I cannot to set any value of inherited BindingNavigator because they are disabled. I need to set "BindingSource" property to the created BindingSource.
Is it possible in other way than at run-time
Stone

Unable to modify VS2005 Binding Navigator in the inherited Form
MSDNuser63
So, people from Microsoft, you should understand that this is very bad bug and i think you lost thouthands customers for this reason. It would be very nice to solve this problem in shortest time...
TopDog
Hope Borland implement it in Delphi 2007. If so than we'll by their IDE.
TheCranker
Joe
MSenthilVel
I understand your frustration around this issue, but we disabled this scenario intentionally (for ToolStrips and ToolStrip derived controls such as BindingNavigator). We chose to not make the engineering effort it would have required to enable this scenario for VS 2005. This decision was not make lightly and we understand customers would like this functionality, but the existing visual inheritance architecture in combination with collection based controls makes it extremely costly to address. We hope to enable this in future versions. Until then, you'll have to use code to achieve this.
Joe
dlldelhi
Hi, in this monthly microsoft release a Service Pack 1 of VS 2005.
When this feature will come back
I did a test with a DataGridView control and the control still disable at inherited form; With a basic controls like combobox, textbox, etc, changes are possible (in inherited form changing control property at disign mode); But with the Inerited controls like DataGridView, Bind Navigator property changes is disabled at Design Mode;
I want put more columns in my inherited grid and I can’t do that in Desgin Mod...
It’s a very usefully feature... Why it just removed when it works fine in .Net 2003
I hope this feature come back so soon as possible... Until we still working with .Net 2003.
Thanks,
Fabio.