Candace, Thank you for the reply.
I now understand the "no reponse" is included as "any response" therefore it is not a bug but kind of a bugger....
I guess a feature request would be to have the option "any field response" included weather the field data was dynamic or static. This would allow focus on the field at hand and not all fields on the form with the same type of event configured. With the current setup, a form may only have one event trigger with the "any response" enabled (for fields with dynamic data).
Please see pic for the box I'd love to see included for fields with dynamic data, but currently only available to static populated fields.
Sorry for the late response, but I did end up using hidden field, but not without the need to add an additional field. Ironically I added a radio button to unhide each field or in effect, swap visibility between the two listboxes. I was trying to avoid the additional "picker" field/radio button, which is why I was originally just trying to hide/swap the relative submit buttons (so user would be unable to pick from field "A" and hit submit button "B").
I then added my custom submit buttons to the footer of each listbox. I now have a decent working form.
To help understand what the issue was, you must realize that my two list boxes are "or" fields, not sub category of one another. Each of my custom submit buttons just redirects to unique landing page for each listbox response.
I do recall originally trying combo boxes, but I cant remember what drove me away. It may have been related to the form being new, and currently the listbox (combo box) only has one entry at this time. If I recall, I was getting false positives/default with one field in the combo. Again not 100% sure what the issue was.
To answer your questions, I'm running DNN v05.06.03 (45) and Dynamic Forms v3.40.20. Wow just noticed I'm behind a major version on Dynamic Forms. Could my feature request already be in there???? LOL
Thanks again for helping me understand the "no response" action.