Again I was not talking about a form submitting to itself.

As far as my comment about not doing params at all, I was referencing doing
them for any of the FORM scope but figured that was obvious by this point.

On 11/17/05, Bobby Hartsfield <[EMAIL PROTECTED]> wrote:
>
> > nor was I talking about doing any params at all.
>
> Maybe this threw me a little?
>
> > cfparam just needs to be done on the PK so that by default
> > it is equal to a non-existant one such as ID = 0
>
> The form submitting to itself (like most do for validation purposes) was a
> "scenario" as to why it's a bad idea to do what you described.
>
> Im not saying don't use any part of your suggestion... just use the query
> results to default values that MIGHT not exist. It will save th user from
> re-entering data they already entered once if any validation fails.
>
> 1) get the query record
> 2) set their values to default form variables with cfparams
> 3) use the #form.fieldnames# from the params for the value attributes
>
>
>
>


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224607
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to