Paul,

Thanks for your reply.  I don't follow you, though.

Here is what the note says on the page to set up alternate form: "If you enable an alternative form action you will loose any cforms application logic (spam security, field validation, DB tracking etc.) in non-ajax mode!".  While it does not explicitly say it, to me this says the cforms application logic does work with ajax turned on.

In any event, I will try your 2 part form idea, as I need to get this to work. 

I think the description said 'you will loose any…' as to not raise any hopes that it would work, again this was meant for developers and not per se a fully functional feature, as I understand it – perhaps Oliver can chime in.

Anyway, per his last post, the next release will support what you've tried to do initially.

My work around merely added an in-between step, so your last/second form in fact has to have

• the same input fields as the 1st (they can be hidden via CSS!)
• and point to the alternative action for rerouting the form data

…or simply wait for v11.7.2.

Paul.

You both were right.

Firefox indeed supported JS based form validation for alternative form actions even though it wasn't meant to be included for starters.

Due to high request I modified the JS part to accommodate cross browser JS field validation *before* the form & field data is sent off to the remote address.

Stay tuned, v11.7.2 is about to be released shortly.

PS: I think Paul forgot to mention that for the workaround to work, both forms not only need to have the same form fields, but also need to have all form fields use the same custom form field IDs (feature must be turned on, too)! The key is, that the form data is sent from form #1 to #2 and that only happens when the field names/ids are identical.