But the accounts must show because the view panels looks like little internal windows above the list. If this doesnt clarify things, just tell me and ill post the whole page with the code-behind. it would still be recommended to do that within a ! also, since we don't see the code within Build Accounts View - make sure you're not doing anything with the formview in there. Now I think like you told, something with the postback cause in the page_load looks like: Wich just gets a list of Accounts and gives it to the lv Accounts and binds it. Anyone see anything strange in my straight-forward code? ASPX Don't know if this will help, but it shouldn't hurt either. Unwrap the Error catching from around the Label1in your onupdated event. I'll try your idea for the Label, but as far as removing the error handling goes, I know it doesn't make it there by fact that it never hits my breakpoint in that method anymore. Thanks again for the suggestions [: D] More stoopid noob tricks. maybe double check that it is hitting the end of the updating event.One more thing, the event fired intially when I set it from the Designer, but no more. And then of course, the cheap work around is to take your code from the 'updated' event and move it to the end of the 'updating' event.
Could you specify the datatype, constraints, name, and all the information about the column settings in your database and be careful and respect the 'case sensitive'. post the complete code to your "Update Report By Id" method.
it turned out, that I forgot to set Update Metod for the Formview.