EDIT: I didn't realize replying to the email I receive as part of my subscription to this thread would enter my response for me. Cool!

Hey Legallogic!What kind of values will the drop-downs have? As for the output field, what kind of values would it have? In other words, are you wanting to add all the values of drop-down lists to the output field as a comma-separated list (i.e. value1,value2,value3)?

Hey rweastmanir!As a simple workaround, I might recommend having a hidden field on your form. In the preSubmit event (client side), I would set this field to some easily testable value like "1" or "DONE". Then, you could just add a script to the initialize event of the form's root node that tests the value of that field. If the value is "1" or "DONE" then set all the fields to "readOnly".Feel free to shoot me an email if you have any questions!Josh BoyleCardinal Solutions Groupjboyle@cardinalsol...

Hey Legallogic!I'm not 100% certain I understand what you are struggling with but I'd be happy to help. If you could provide an alternate explanation of your issue I'll take a look and help you solve it. What I *think* you're asking about is in reference to the test case of a switch statement. Typically a switch would be used to test the value of one particular variable, so:switch (varTest){ case "A": //Do something here break; case "B": //Do something else here break; default: //Do something co...

Hey Kyle!The Validate and Calculate events are both responsive events meaning that they always fire in response to other events. When you exit a field, the Validate event for that field should fire. My recommendation would be to leverage the Validate event for your validation as opposed to the Exit event and to ensure that each Validate event is set to run client-side (select "client" from the "Run At" option within the script window.I apologize in advance if you are already familiar with the Va...

Hello drcaesar-21qe0k!Any form node (Text Field, Drop-down List, etc) has a method you can invoke called "execValidate". This method invokes both the pattern and the script validation for the given node - in that order. If you had a form with a text field entitled txtTest for which you would like to run the pattern validation on, you would simply type:txtTest.execValidate();Please let me know if you have any questions!Josh Boylejboyle@cardinalsolutions.comCardinal Solutions Group

Just thought I would reach out one last time on this topic. To be more specific, I am looking for a means by which to "turn off" dialogs within a Designer 8.2 form. I still wish to use Validation patterns and perhaps Validation scripts but I don't want any dialog boxes to appear should any pattern or script be violated.Any help would be appreciated.Thanks in advance!

Hello Amit!It is true that LiveCycle 8.2's JDBC service has on built-in exception handling. This has been remedied in 9.0 as there are now several exception types that can be handled.If I understand correctly, your trouble comes with the lack of transaction management around the existing JDBC service within LiveCycle. To this I can only recommend that any SQL statements needing to be run with transaction management be done so within an executeScript service. I have, on many, many occasions, util...