Hello, Chad.
I've installed your latest fix and yes, the radio button validation error message is displaying properly now. Nonetheless, the newly created question with radio buttons now have the "Default Value" forced upon it (ie, there is an automatic selection--generally it is the last option in the list.) You can actually see this happening if you create a radio-button question with the "Advanced Field Options" expanded and keep one eye on the "Default Value".
With versions before the latest one you sent me yesterday, the "Default Value" started out with no option selected. In any case, my 2 forms were created with the earlier versions and the "Default Value" with no selection remains intact, so it is okay for me now because my immediate concern is to simply finish this web site and let our client test and launch the site. You may wish to investigate the reason for the now automatic "Default Value" for future refinement.
I am also listing below a number of considerations for refinement in your future upgrades, and I think it is worthwhile to look into them:
* A style class for the server-side validation error messages
- Currently I must use the trick I used previously--before you added the style classes for the client-side validations (such as DynamicForms_Summary, DynamicForms_RequiredField, DynamicForms_Compare, DynamicForms_Regular) . . . having a separate style definition for each form module ID#.
* The Combo Box Question Type
- You mentioned in an earlier message that the way server-side validation works is by not allowing the first option in the Combo Box to be selected, and generally this option would say something like "-- Select From DropDownList --". Now I've noticed that I can only implement this with "Enter Options" Question Options. If I use "SQL Driven Options" to query my DB table and then populate the option list, then even though my DB table has an entry for "-- Select One --" (not the first row in the table), I cannot move this "-- Select One --" option to the topmost of the option list (because all options are greyed out and not selectable for manipulation.)
So this is a problem for people who use the "SQL Driven Options" and want to employ validation for the Combo Box.
I also noticed that even with the "Enter Options" Question Options, if the first option is not something like "-- Select One --" but one of the real options, then validation does not throw an error if the first (real) option is selected. But this is a more minor issue than the one just mentioned for "SQL Driven Options".
* Date Question Type
- How about adding a "Date Display Type" of a simple textbox (since only textboxes are validatible with ASP.NET)--one not with the pop-up calendar? The fact is, this calendar presents a rather awkward usability issue . . .
. It is not immediately intuitive or obvious that one should find the desired year by clicking the year link to move back and forth in time.
. One must click many, many times to get to one's desired year.
. Then one must click some more to get to one's desired month.
We are an advertising company and we are all about delivering the message as quickly as possible by making things as user-friendly and usable as possible for our audience. Our creative people really were not very thrill about this option, but it's the only one we've got now since our client needs the validation.
Well, in any case, this is a wish list for your upcoming upgrade, and with your (or your team's) expertise, they are not likely to be major hardship.
Once again, thank so much for all of your tireless support and a remarkable product.
Best regards,
Jennifer
Agent 16