Thread: Integrating a GridView component

Has anyone successfully used a gridview component with the ASPDotNetStorefront DB class.

I'm creating a custom page that will be using a GridView component to capture data to a new table I added. However if I use the DB.FillDataSet function to create the data source for the control, I get an error message when a postback event executes on the page. The following message occurs:

Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.


The problem does not occur if I make the connection using a SQLDataSource component. I would prefer to use the DB class so that I do not have to maintain two separate connection strings.

Thanks,

John

Sounds like databinding issue not inherent on the DB class.
Take a look at this blog:

http://weblogs.asp.net/davidfowler/a...acontrols.aspx

In the PageLoad event, just set the SqlDataSource.ConnectionString property to DB.GetDBConn() That will override whatever is coded into the SqlDataSource control with the value from your web.config. That may however prevent you from working with the gridview in design mode. We've run into the same here on some of our custom licensing mods using the RADGrid, so generally what we do is hard-code our dev environment connection string in the control declaration on the ASPX page, but use the trick mentioned previously to override that on page load with the DBConn string from the web.config. Then the control works in both design time and production runtime.