Hi Guys,
I've been using your Grids for quite sometime now but theres a bug thats really getting on my nerves!
My program uses a series of class objects as datasources, these are databinded to the grid at design time and i use the supplied designer to Rename/Hide/show and Resize the columns.
Now the program is starting to get quite large and at least once every couple of days now i'll be doing some work on a section that i havn't touched in days and realise that the Grid has lost all its formatting ... All the hidden columns are now showing, all the column headers that i renamed are lost and the resizing seems to be lost aswell.
I've just had a phone call from an end user who has just reported that a large grid has just lost all its formatting, even though i sat down with the my director only two weeks ago and designed the grid for him!
Does continuing to use your grids mean i have to continually mantain them and check for this bug or is there a fix for this problem??
Acording to the project upgrade utility i am using 2007 Vol 2 for .NET 2.0 and the project that has just gone wrong is using the Infragistics2.Win.UltraWinGrid 7.2 (7.2.20072.1063)
If you are not modifying the data source at all, then my best guess is that the data source is sending Reset notifications for some other reason. Maybe it's happening during the InitializeComponent while the datasource is being built. I really couldn't say.
I typically try to do all of my grid initialization in the InitializeLayout evnt (at run-time) whenever possible, so that I can avoid problems like this. Also, you might just want to save the layout of the grid to a file at desing-time. You can do this using the Layout Wizard. That way, if it gets lost, you can just re-load it.
Since making the first post i have now upgraded my project to the latest version of Win Forms Vol 3 (7.3.20073.38)
I've logged back on seeing if anyone has a solution to this because its just happened again to a different grid ...
To my knowledge i have not changed the underlying datasource in any way ... in fact i havn't touched it for weeks.
Steve - i've now designed a quick app that i use to backup my project to a network share. I'll do as you say cheers...
Infragistics, do you have any methods to avoid this problem in the first place as its driving me nuts!
I've experienced this problem too. I believe it occurs when changes are made to the underlying dataset that the grid is bound to.
To work around this annoying problem i do the following:
1) Close the project
2) make a backup of my project
3) Re-open the project and make sure that the forms using the dataset are closed
4) modify the dataset
5) close the project and if requested I do not save any changes to the forms that use the modified dataset
6) open the project again and proceed as normal.
7) if necessary I restore the form from my backup
Any one else have an easier method to overcome this problem?