Also, none of this data inputed is showing up in the Tracking Database either.  

When you include the full data block (blue box with user data) in your email, do all the radio fields get added then?

Also, none of this data inputed is showing up in the Tracking Database either. 

That's quite odd.

Well, I put the fields above Captcha and CC and they appear in the emial now.

That's another oddity,I wonder why the order makes any difference.

With the old order, did it matter if you turned Ajax on or off for the form?

Did or does it matter if the radio buttons are all selected (either option)?

Also I put in the CSS |fieldsetclose| like a sample form. 

Fieldsets are a good thing to have (structurally) but not a requirement.

Would you mind sending me your full backup form (the one that didn't work per email -> inside cforms.php) so I can take a look?)

Ok, I found the one step that lost all data from being placed into the database and thus email.

First move was removing the fieldsetclose and it still worked.

Second step I moved the "Visitor Verification Q&A" above the radio buttons and this is what killed the info from being passed.  Not sure what this means for you, but this is the issue obviously.

Hope this helps.  I will be making sure for now that "Visitor Verification Q&A" is below everything.

Very cool, yes, I would appreciate that.

I had another inquiry about creating something based on this form. 

As you saw I was doing a weekly football pool.  I am also doing an NFL eliminator challenge that allows for each user to pick only one team each week.  If they lose, they're done, if they win, they move onto the next week.  The clincher is that they cannot pick that team again.  Is there any way to have the data check to see if that user has selected that team (choice) already and maybe grey out that team, so they can't select it or something of that nature.  Does this make sense?

Lastly.....is there any way to show a confirmation page of their picks, versus making the form disappear or do nothing or redirect to another success page?  In other words....once they hit submit, they see their submission right there.  

Thanks!!

Oliver said:

If you need to on-the-fly change attributes of a field based on a logged in user, you need to use cforms dynamic form capabilities.

In the success message you can reference any form fields. Now if you want to include logic into the success message, e.g. only show the selected teams etc. you need to in addition use my-functions.php filters (non-ajax is enough if you use dynamic forms!) to fill a hidden field (used as a proxy container), which in turn you can reference in your success message.

re. the last point there are at least 4 posts (some very recent) that detail the steps.

WOW!  Way over my knowledgebase bro.lol.....but thank you.  And again, thanks for everything, I appreciate your continued assistants in your creation!  It's a great tool.

Never heard of such a thing.

But it depends on your provider and the package you have bought. If they're extremely restrictive then yes, any new plugin with additional DB queries & new data records could cause the system to stall.

PS: To put their response into perspective: I'd ask them how many SQL queries / sec are deemed ok and what your average was. I'm nearly 100% sure they are not able to give you an answer...

If 40+ users submitting a day brings the server down, I'd immediately switch providers.

I know that cforms tends to be PHP Mem hungry, but have never heard of *any* SQL query issues. Also, 25 persistent connections to me only means that the max allowed concurrent users (and thus creating a connection) is 25. This per se doesn't imply the number of SQL queries, though.

If worse comes to worse I'm afraid you might have to turn off cforms. But I'm quite sure that if you start adding other plugins to your site, you'll soon hit a wall again.

PS: Another way, of bringing down SQL queries is to install a cache plugin ("Super Cache" or "WP Cache").

UPDATE:

Well after tooling around the all my plugins, it looks like WP-Sticky was the bad database. I have reinstalled cformII and everything is working again.