If your going to manual export change the value of the radio in the myformname.html.
Yes, I know. I mentioned in my first post that if I manually edited the html code, then I could 'get it to work'. It's these extra steps that I was trying to avoid, considering that for any further changes to the form using WFB program would also require these manual changes as well. Not terribly user-friendly since the program almost does the job.
I re-read the documentation on how parseInt works (above). What I believe is happening is: "If the first character cannot be converted to a number, parseInt() returns NaN". Since parseInt sees a string like "Single:25.00" it returns a NaN, since the first character is not a number, but text. It's unfortunate that it would not "find an occurrence" of a number anywhere within the string, but it doesn't. Are you aware of another function that does? I think that would solve the problem.
Alternatively, if the program (WFB) would ONLY code the value of the radio button, instead of inserting the complete text label AND value, I'd be well on my way. So, I guess I'm faced with doing it the hard way, which is unfortunate, because for my proof-of-concept I will be simply uploading my form to S-drive, which doesn't allow me to directly edit the html file.
Thanks for all your help!!
Norm