HTML Form Will Not Submit, Likely Form Validation Issues

Please note, this unresolved question has been posted to another site. While I do not feel that an answer from that site is likely at this point in time, I would recommend a quick check to ensure the question has not been answered before putting in time reviewing this! My intention is to not waste your time!

---------------------------------------

The following code works just fine when it comes to completing the form located on the webpage. The issue arises when it comes time to submit the form.

This appears to be some an issue with validation, as when the form is completed systematically, the submit button is disabled. However, when I go back over the text boxes and manually type in the exact same information, the submit button then becomes available. I believe the form thinks it is incomplete, thus disabling the submit button. I even systematically reenabled this button using SubmitBtn.disabled = False (which allows it to be manually or systematically clicked), and it still will not submit.

I have never encountered this type of form validation when filling in webpages.

I am currently on Internet Explorer 11

The following code is complete and can be tested without needing modification. This is a website that is made available to the public

Please Login or Register  to view this content.

Please Login or Register  to view this content.

Originally Posted by AlphaFrog

Activating each required field seems to enable the Submit button.

Please Login or Register  to view this content.

That did not solve the issue unfortunately. However, because of your response, I cheated and added reference to Microsoft HTML Object Library. I declared one of the boxes as HTMLInputElement (temporarily, since I must use late binding), and went down the list of every possible culprit that looked like it could help. Here's what I used for each object:

Please Login or Register  to view this content.

I ran the code and it worked. So now it was time for process of elimination. I determined the issue lies with the .setActive property.

Again, thank you for your assistance! I would have likely been stuck on this for another month!