I was needing to create a grid control for my .net app, which will consist of an updateable grid that will allow certain rows to be editable, and certain rows to be non -editable. I also want every new row to show drop down controls for each field, and when the user clicks a '+' icon on the actual new row, the grid should add a new row. When the save button is clicked (not on the grid), the dropdown controls should be removed and the text that the user selected should remain. The user should also be able to click a 'X' icon on each row to delete that particular row as needed. Should I use the Infragistics gridview or asp.net gridview control? Is there any sample applications I can use as a guide?
thanks.
Hello,
Thanks for writing. Of course it would be much easier to achieve this with Infragistics UltraWebGrid (and some of the features you have described are not even possible with the standard asp:GridView control). I believe one of the best guides on the internet about implementing UltraWebGrid is the following great whitepaper:
Quick Guide to Implementing the NetAdvantage UltraWebGrid in a Real Life Scenario
http://dotnetslackers.com/articles/aspnet/QuickGuideToImplementingTheNetAdvantageUltraWebGrid.aspx
Hope this helps. If you have any specific questions, please let us know.
Thanks for the quick reply. Exactly which features cannot be implemented in .NET grid view? I just came across applications written with the .net gridview and it looks like everything can be done, except I didn't see the dropdowns being kept as dropdowns on all rows that weren't saved, but I'm sure that is possible, as there is an edit button that turns the particular row's fields (that are being edited) into dropdown boxes. Also, I've successfully implemented Infragistics treeview with no issues (on a different part of the application), but what about speed? Is the .NET gridview much faster than infragistics ultrawebgrid? That would be an issue that would affect my decision.
Thanks.