In my experience CFForm is more trouble than it's worth. I generally just use regular forms + jquery to get elegant client-side validation. Much more lightweight and gives much more granular control over your form.
On Thu, Feb 17, 2011 at 5:27 AM, Torrent Girl <moniqueb...@gmail.com> wrote: > > The solution was not to use CFFORM at all. it now works. > > > > I have a simple one: > > > > <cfselect name="endampm" required="yes" message="Please select an > > AM/PM for the end time" id="endampm"> > > <option value=""></option> > > <option value="AM" <cfif schedule.endampm EQ "AM">selected="selected" > > </cfif>>AM</option> > > <option value="PM" <cfif schedule.endampm EQ "PM">selected="selected" > > </cfif>>PM</option> > > </cfselect> > > > > > > >depends on cfselect... > > > > > >in simple cfselect - one based on an in-page query, for example - you > > > > >can provide a value in the 'selected' attribute and an <option> with > > > > >that value will be pre-selected. > > > > > >advanced cfselect - one with a binding - does not support this > > >functionality. but there are javascript work-arounds for that: google > > > > >'cfselect binding selected' and you will find them > > > > > >Azadi > > > > > >On 16/02/2011 21:34 , Torrent Girl wrote: > > >> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342373 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
