I have a DetailsView bound to a Sql Server datasource

When i click the "update" button, a stored procedure is executed, which tests to see if the submitted values are appropriate and returns an error message if the item could not be updated.

However, because the DetailsView re-binds on a post back i have now lost what i have typed into the boxes.

Sure, i can manually save the entered data into variables during the DetailsView_OnUpdating event and recall these, if necessary, on the DetailsView_DataBound event but this is very time consuming.

Is there an easier way? Thanks in advance

Hi,eamonroche:

I suppose that you can use viewstate to set and get the value you typed.

Use viewstate?

Do you mean through the DetailsView_OnUpdating and DetailsView_DataBound events still - or do you mean something else?

Thanks

Use viewstate for storing your data.

http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/

Don't do that, it will lead to poor performance and probably not help you

 You will have to avoid rebinding the data to your datacontrol when the page is posted back.  In the Page_load event handler use IsPastback to control this.  Once you have stored the data then call your databind method.

private sub Page_Load [Handler Code will be here] 

 If not ispostback then

    BindData

end if

end sub

private sub UpdateEventHandler

 ''''' Store Your Data here

BindData 

end sub 

thanks docluv

but the databing for a detailsview is done automatically...there is no explicit BindData function that i can disable within an "If not ispostback" question.

it would be great if i knew how to turn off this automatic databinding

Hi, if you want to disable the automatic databinding you could do the following in the page load:

 
If IsPostBack then

    DetailsView.DataSourceID="" 

end if
 

This will unbind the DetailsView from the sqlDataSource Control

Regards,

Craig 

Thanks Craig. I will try this.

Eamon

Hi Eamon

On second thought you may need to put this in the Page_PreLoad event. The onload even may be too late and may have already encountered the error.

Regards,

Craig