Why not create a cfc that makes your form and validates it on both sides? Then integrate it with your security to confirm that the user has rights to update that field before allowing state or database alteration. DRE
On Tue, 22 Mar 2005 13:31:47 -0600, Dawson, Michael <[EMAIL PROTECTED]> wrote: > ....especially with all the new mobile web browsers that may not support > JS. > > M!ke > > -----Original Message----- > From: Erika L Walker-Arnold [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 22, 2005 1:14 PM > To: CF-Community > Subject: RE: client- or server-side, or both? > > Personally, no matter what, I'd do server side first. Get it functional. > And working. > Then add JavaScript as a backup. > > Cheers, > Erika > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:151491 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
