We're using NetAdvantage for ASP.NET version 9.1 and have some users reporting problems when they access our site with Firefox or Chrome. Under Firefox, we've found that the UltraWebGrid appears normally but does not function well. Under Chrome, the headings appear but no data. We also have issues with the UltraWebMenu control. I've noticed that version 9.2 says it supports Firefox and Chrome for the AJAX controls. Would upgrading to 9.2 help our issues with the UltraWebGrid and UltraWebMenu? We've looked at the WebDataGrid but it does not handle some of the features we've used in the UltraWebGrid. If we need to support these other browsers soon, what's our best course of action? I've seen some posts in the forum that indicate some people are using the grid with Firefox. Is there some trick to making it work? Maybe they only display data without editting?
Thanks.
Hi Frank,
We've added more features to the WebDataGrid since 9.1. What features did you find missing back then? I can let you know if its already available or not.
The best course of action would be to replace the WebGrid with the WebDataGrid or the WebHiearchicalDataGrid (based on your usage) to support Chrome. Same with UltraWebMenu to the WebDataMenu.
If you have any questions, feel free to ping me: murtazaa@infragistics.com
-Taz.
Hi Taz and thanks for the reply. I checked the features on your website and understand that the WebDataGrid does not support multiple bands. That's a feature we use extensively. There are probably others but I stopped looking after I discovered that it didn't handle the multiple bands.
I also understand there is no migration from UltraWebGrid to WebDataGrid so it would be like starting over and we have over 50 screens that use the grid..
Just to clarify, I believe by multiple bands you mean hierarchy. WebDataGrid is a flat grid, if you need hierarchy, then you need to look at the WebHierarchicalDataGrid.
There is no migration tool, unfortunately. There are a lot commonality as both are grids with rows, cells, columns and bands, but there are APIs changes that you will have to make in order to migrate.
If there is anything we can do to help, please let us know.