Assisted Solutions Forums

We are moving from v2 to v3 and experiencing an issue with the new ProgressDisplay control. Our forms all use client-side javascript validation (in the form onsubmit event). The issue is that the ProgressDisplay control automatically fires before our onsubmit event instead of after (part of the binding to the submit buttons I presume), which basically renders our validation useless. 

My question is: How can i fire my form validation javascript routine for onsubmit prior to the firing of the SlickUpload_Submit() that is added by the ProgressDisplay control?  I would definitely prefer to leave my buttons as submit buttons rather than changing them to type=button and handling this all manually.

You should use the UploadManager control. Set AutoUploadOnPostback to false on the control, and then after your validations are complete, call SlickUpload_Submit() to actually submit the page and start the upload.

There are several file upload fields in this form that need to remain where they are.  In this case, should I be using the ProgressDisplay control for a more customized approach?  The UploadManager control automatically generates a file upload form control that I don't want to appear.  My goal is to have a single progress display for the 4 file upload fields on the form - without moving them and after javascript form validation is run.

Ideally, I could set AutoUploadOnPostBack to false for the ProgressDisplay control, and follow your previous suggestion?  I don't believe this control supports this property, however.

Thanks much!

Can you email a screenshot of the page in action with a copy of the source and codebehind? That way I can get a better idea of your scenario and suggest the best alternative. chrish at krystalware dot com.