Thanks for the response. I get the drop down list populated on the page load fast so I think that's ok. It's when I do a partial page update with ajax is the issue. I made all of my updatePanels conditional with no effect. It doesn't seem to matter if the dropdown is in an updatepanel or not, though I've read having a dropdown with thousands of options in an updatepanel is bad news. Using firefox with firebug, I was able to get more of an idea what's happening. I don't understand it, but I have more clues. If I databind the dropdown box, I get a bad AJAX post response about validation. Without firebug installed, the response would seemingly hang the browser. Without the databind call on the dropdownlist I get no such validation error returned from the ajax post. Below is the AJAX response error.505|error|500|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.
If I don't bind DropDownListBilling, it's not in the post and I dont' get the error. I dont' understand why it's even in the post since it's outside an update panel.
If I add EnableEventValidation="false" to the top of the page I don't get the error in firefox, but my IE still hangs... maybe since it's old ie 6. I'm interesting in understanding
why this databind causes validation problems in the event. Below is the Post which gives me that error.
DropDownListBillingCompanyName 2217
S1
ScriptManager1 UpdatePanel3|btnPrevRecord
__ASYNCPOST true
__EVENTARGUMENT
__EVENTTARGET
__EVENTVALIDATION /wEWDALjtbrgBQLR3v1hAoXnv9MCAsSEqIMOAu+ymIwNAvzy8KMMAoOQiL4EAoGx7IIJAo2R+JIOAuC5/8wMAvmGnOwPApvRtIcEfSGzvVF3Jk2U5VmL9OjYmyJbIZw
=
__LASTFOCUS
__VIEWSTATE /wEPDwULLTEwNTY0ODM4MDRkGAEFF0dyaWRWaWV3UHJvcG9zYWxEZXRhaWxzDzwrAAoBCAIBZPPeKhiGrKIT8VPffxbdPFzQyuvM
btnPrevRecord Prev
txtDate 3/9/2009
txtProposalNum 21596
txtPurchaseOrder
txtRecordNum 296
it takes me 2 clicks on the prev record button to get the error. Strangely enough it will go to the first previous record. There is something interesting in the first post request that isn’t in the second.
__EVENTVALIDATION (Very Large Data)