Assign cfinput checkbox value

Question

I have following code to assign value from my stored procedures.
The text cfinput works to get value from stored procedure, but check box does not get value.
The check box value return to 1, but check box does not check.
I would like to know are there any way to assign a stored procedure value to check box.
Your help and information is great appreciated,
Regards,
iccsi,
<td><cfinput type="checkbox" name="Mychk" id="Mychk" value="#MySP.MyCheckValue#"></td>
<td><cfinput type="text" name="Mytxt" id="Mytxt" value="#MySP.MyTextValue#"></td>

Answer 1

fergusondj wrote:
First, you are completely wrong here.  As I stated before ColdFusion will not omit anything from the form scope.  It has no control over what the browsers sends to the server.  The form field omission is done by the browser.  There is nothing for CF to omit as the field would not be submitted by the browser.
I hope you can see that your arguments have leaned so far on misunderstandings. This time you make a shift within 3 sentences from 'scope', the word I used, to 'field'. The shift is subtle, but makes all the difference. The form scope I talk about pertains to ColdFusion, not to the browser.
To illustrate with a concrete example, suppose the form in question has a checkbox named chkbx. Suppose further that you submit the form without checking the checkbox. Then, on the CFM action page, ColdFusion will omit the key chkbx from the form structure. This is simply a statement of fact. It is true, whether or not the browser sends the field to the server.
Next, again you are completely wrong about the use of any of the cf ui tags (cfform, cfgrid, cflayout, etc.. ).  These should not be used by someone learning CF, or anyone else for that matter.  They don't teach you CF, the teach you how to do crappy UI that will not translate over to any other technology.  A new developer is better off learning JS and how to build forms properly so that knowledge can translate to other languages.
If you were to look in StackOverflow you would people consistently trying to get people to not use the UI tags.  Anytime someone posts a question about any of the UI tags, one of the first comments are generally..  "stop using the ui tags".
You might want to read this blog post...
http://www.raymondcamden.com/index.cfm/2014/1/23/Im-not-going-to-tell- you-to-stop-using-ColdFusion-UI-tags-anymore
Then check out..
https://github.com/cfjedimaster/ColdFusion-UI-the-Right-Way
Once again, you claim I am wrong when I mention another statement of fact. I have been around for a bit as a ColdFusion developer and am aware of the the issues regarding the UI tags. In fact, I myself have had to resort over the years to alternative solutions like Dojo, Ext and JQuery. However, this isn't about me.
Many colleagues use - and, if recent history is anything to go by, will in the near future continue to use - ColdFusion's UI tags. Especially, a lot of developers starting out in ColdFusion consider them simple, versatile solutions to their problems. Rightly or wrongly. That is simply a fact of life.
Naturally, I agree with you that more experienced developers owe it to the community to sound a note of warning about the issues that may arise with the UI tags. However, I do believe that such advice will be more effective if delivered with a tickle rather than a punch.
In my opinion, there is a psychological component to this. People invest time to learn ColdFusion, and good money to acquire a license. They want to believe in all the goodies the platform promises to deliver. They would hate and resist you if you attempted to spoil the dream for them. Ironically, your reference to Raymond Camden actually says something similar.
This reminds me of one of the best books on strategy I ever read, David Maister's Strategy and The Fat Smoker. Why would an intelligent man, a professor at Harvard, no less, continue to smoke, put on weight and avoid exercise even after his physician warns him of the impending danger to his heart? The answer is trivial and universal. It has little to do with rationality. The professor or the ColdFusion developer, like most human beings, prefers the easy life, wants to believe things will work out somehow today, and puts off difficult changes until tomorrow.