Detailsview fired event itemupdating which wasn t

However, although the Validator was set to Invisible, the underying validation still took place upon 'Update' button click.Unfortunately, error message from this Validator was suppressed ( I guess most likely because of its Invisble nature ). If you set the Button's Use Submit Behavior property to FALSE, it works! Why do the solutions seem to conflict in reasoning? my case is i use updatepanel, so i need to wrap everyting include the objectdatasource with in the update panel.

(3b) Then I copy and paste the exact coding from the problem aspx to ....this modified works, to my amazement !!! This aspx works......until not knowing when.....update command problem happen again.When optimizing for these considerations, you might find that building data-bound applications by using the server controls in ASP. What I have done to narrow down the problem: (1) Replace Object Data Source with an equivalent Access Data Source : same problem.Such exception is probably aroused when ODS's do not match ODS Update Method's parameter.When I finally resort to set the Update Method's parameter manually, everything works!

Search for detailsview fired event itemupdating which wasn t:

detailsview fired event itemupdating which wasn t-81detailsview fired event itemupdating which wasn t-57detailsview fired event itemupdating which wasn t-86

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “detailsview fired event itemupdating which wasn t”