I am using the latest ultrawebgrid & asp.net3.5
I have an object data source(list), bind it to a simple grid using InitializeDS(Not in a WARP, AJAX enabled )
The grid has check boxes, I am handling updatecell to track the state of the checks.
I update the Database in updatecell depending on the state of the checks and have to reload the grid.
I am trying to assign the updated DS to the grid and call DataBind in UpdateCell.
Running into the following exception:
[NullReferenceException: Object reference not set to an instance of an object.] Infragistics.WebUI.UltraWebGrid.UltraWebGrid.UpdateDBRow(UltraGridRow row, UltraGridRow oldRow) +155 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.ProcessChanges(StateChanges stateChanges, Boolean fireEvents) +1559 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.RaisePostDataChangedEvent() +161 System.Web.UI.Page.RaiseChangedEvents() +165 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1485
I tried setting the DS to null and binding to a null DS( came across these in the forums)
Any thoughts or ideas why this is happening?
thanks,
sam
@samr:Did you find a solution? I have currently the same problem after updating from Version 8.1 to 8.3. I use a simple webgrid with no ajax or warp or anything else and do update to my DB-Server in UpdateCell and calling inside UpdateCell "DataBind" of the webgrid. BANG!! Same error as you described...
@Infragistics:It is possible for you to release new versions without having new problems/bugs on every update? As it seem: NoAnd no, there are not too many things here!!! Build your own quick example. This is done for you in few minutes!
There are too many things that could cause a NullReferenceException in particular circumstances - and most of them would be expected. We'll likely need to inspect a sample project to determine what is causing the issue here, and determine how to prevent it from happening.
I suggest that you submit a support request and attach a sample project that we can run and debug that demonstrates this exception. We can then use this sample to determine why this is happening. If you need to use a database, connect to the Northwind database, either in Access or SQL Server.