| | | StrataFrame Beginner
       
Group: StrataFrame Users Last Login: 2 days ago @ 1:44:06 PM Posts: 42, Visits: 943 |
| | I have a web page with a WebBusinessBindingSource and an Infragistics UltraWebGrid. (2007.3) When I try to set the grid's Datamember property i get the following message: Nullreference Exception Object reference not set to an instance of an object Source: Microfour Strataframe Extensibility Stack Trace: at Microfour.Strataframe.Extensibility.WebBusinnessBindingSource.GetView(String viewName) After that, everytime I click on the grid I get the same message and have to click on the OK button several times to get rid of it. |
| | | | StrataFrame Beginner
       
Group: StrataFrame Users Last Login: 2 days ago @ 1:44:06 PM Posts: 42, Visits: 943 |
| | (the grid's DatasourceID is set to the WebBusinessBindindSource) |
| | | | StrataFrame Beginner
       
Group: StrataFrame Users Last Login: 2 days ago @ 1:44:06 PM Posts: 42, Visits: 943 |
| | Forget it. I installed in a clean machine and it works Ok. Sorry. |
| | | | 
StrataFrame Developer

Group: StrataFrame Developers Last Login: Today @ 11:13:06 AM Posts: 4,104, Visits: 4,176 |
| No problem...glad you got it working |
| | | | StrataFrame Beginner
       
Group: StrataFrame Users Last Login: 2 days ago @ 1:44:06 PM Posts: 42, Visits: 943 |
| | After upgrading a solution from VS2005 to VS2008 I get the same error. Where should I look to try to fix this? |
| | | | StrataFrame Beginner
       
Group: StrataFrame Users Last Login: 2 days ago @ 1:44:06 PM Posts: 42, Visits: 943 |
| | I get this error whenever I click on the Infragistics grid |
| | | | 
StrataFrame Developer

Group: StrataFrame Developers Last Login: Today @ 11:13:06 AM Posts: 4,104, Visits: 4,176 |
| | More than likely when you upgraded, a bunch of "junk" was added to your web.config file. Restore just the web.config file to the previous version to see if your error goes away. They added a lot of tags that can cause issues. If you use source control then this shouldn't be too hard...just restore the web.config file and keep the previous version and it should make things more smooth. But whether it will resolve this particular issue I am not sure, it is just the first place I would look. |
| |
|
|