I keep getting the following error message when I run my application. It matters not if I select Yes or No, it keeps appearing. At some point in time it will stop. How do I make it really go away?
May be a bit late now but I was getting this as well... I had to clear the bindingsource.datasource and just assign it at runtime... no more message.
I explained where the setting is in my previous post:
<Infragistics> Mike Saltzman said:You can turn off the automatic generation of ColumnSets by setting tree.ColumnSettings.AutoGenerateColmunSets to false. But then you will need to generate the ColumnSets yourself. Or perhaps set this property back to true in the form's constructor (after the call to InitializeComponent).
The type of data source doesn't matter. This property determines whether the tree automatically generates the column structure from the data source or expects you to do it manually.
The message you are getting is there to warn you that the structure of the data source has changed and that therefore the column sets in the tree may be out of synch. So it gives you the chance to update the column sets based on the new data structure or keep the existing ones.
I am always data binding all container controls to BindingList of custom written objects. I am never binding an Infragistics control to either a DataTable nor UltraDataSource. What impact would it have on me if I did turn off AutoGenerateColumnSets?
And is that a system wide switch? How do I turn it off?
Sam
Hi Sam,
I know what you mean.
There's not much more I can do at this point without being able to duplicate the issue. For a problem like this, you probably won't be able to create a new project and build up to it. So I'd recommend taking the opposite approach. Make a copy of your real application and then start removing pieces of it one at time until you've narrowed it down. If you can post a sample of a reasonable size that I can run here without having to access your data source, then I can take it from there.
If you just want to move on with your project without spending any more time on this, then I'd recommend trying the workaround for now. Turn off AutoGenerateColumnSets at design-time, and then switch it on at run-time in the form constructor and see if that helps.
Mike,
I don't think I could reproduce this problem very easily. For one thing, Visual Studio isn't crashing anymore. I changed something, don't know what, I am changing a lot of code all over the place, but something has changed and Visual Studio doesn't crash now. The dialog still appears, but no crash.
Computers are, well, their won creatures, anyone that thinks we actually control them is fooling themself.