Hi,
I'm very new to web development and the UltraWebGrid :-) I have a very simple UltraWebGrid within an asp:wizard control. I manually add rows to the grid as the data is not coming from a database as such. All is fine so far and I have implemented my own crude form of 'move row up/down' to allow ordering. When I click on the cell which contains a button, after my server side button handler is called I receive a JavaScript error as above. I also get this same error when I simply move to the next page in the wizard so I guess it is as a result of a postback in the grid.
I have no idea what could cause this as the error appears to be coming from the grid which is as I said very simple. Any ideas are most welcome!
Hello,
It seems the JavaScript error is raised after a postback. However, in order to nail down the issue, I would like to clarify few things. Here is my list of questions:
1) Which version of NetAdvantage controls, Visual Studio and .Net Framework are you using?
2) Are you using AJAX? If yes, then are you using Update Panel or the built-in AJAX of the UltraWebGrid?
3) Which client side and server side events are you handling on the Grid?
4) What is the exact error message are you getting?
5) What happens when the Grid is outside of the Wizard control? Do you still get the same error?
Please let me know the answers in details.
Thanks
Hi Sarita,
I am using NetAdvantage 8.1 - the full version is 8.1.20081.2058. Visual Studio 2005 and .NET 2.0. I my using the grid in its simplest form - just to show a list of items which I dynamically create by adding rows and cells to the grid. I have ensured that the rows/cells are included in the ViewState. I do not subscribe to ANY client or server side events. The grid is flat - I only use one band which actually only contains 3 rows each with 4 cells. I have tested with pure text cells and still get the same error.
I have attached a screen shot of the error I get. I haven't tried the gird outside of the wizard yet but I would guess if it did a post back then the error would occur. Another post has suggested that 8.1 is not compatible with IE 8 which would be a shame as I won't be able to upgrade just to fix this and will probably have to do without the grid :-(
Ok I have not updated the dll into my project folder.After updating that the java script error is got fixed.
I have download the current service realease for infragistics 8.3.But still problem is same.Every I visit the page which has got an infragistics grid then on load and unload of page this error pop ups.
Please suggest us.This problem is really testing my temprament.I can't figure out it is an IE 8 issue or Infragistics 8.3.
Take a look at your registry, in the following location, and you might see the following (or similar) values. Try removing the items for CLR 3.0.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform]
".NET CLR 1.1.4322"=""
".NET CLR 2.0.50727"=""
"InfoPath.1"=""
".NET CLR 3.0.04506.30"=""
".NET CLR 3.0.04506.648"=""
".NET CLR 3.5.21022"=""
".NET CLR 3.0.4506.2152"=""
".NET CLR 3.5.30729"=""
I came across this issue and also reported it to our development team. I'm not sure if you are referring to the recent Service Release 8.3.20083.2102 (released on July 28th) or the previously released 20083.2021(released in Dec of last year). I've tested my sample with the latest released Service Release and it's fixed.
I would recommend downloading the recent service release and testing the application. Please visit the following link on how to download and install the latest Service Release.
http://blogs.infragistics.com/blogs/vince_mcdonald/archive/2009/06/25/service-release-published-netadvantage-windows-forms-and-asp-net-june-25-2009.aspx
If the issue still persists, then please submit a support request with our Developer Support Team by visiting the following link:
http://ko.infragistics.com/support/default.aspx#Overview
Sarita
I forgot to mention this in the above post, but these errors starting showing up in code that has not been changed in quite some time. I can't be sure, but I didn't start noticing them until the 2008.3.2021 build came out, unfortunately I cannot revert back to an older version to test at the present time.