You were exactly right, changing press_date to pressdate fixed the problem.
It did work as form.press_date but not as attributes.press_date. Live and
learn, I thank those of you who reponded, I know it is a fairly newbie issue
:)
-----Original Message-----
From: Michael 'Maxx' Porter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 16, 2001 2:44 PM
To: Fusebox
Subject: RE: attributes.whatever not showing up when passing form
variables to a sql query
when you use XXX_date in a form name CF tries to validate the field as a
date try XXXdate. There are a few other keywords That do this too, I do
not remember them off hand..
At 08:44 AM 1/16/01 -0800, you wrote:
>Yea, thanks for the responce, the error is:
>An error occurred while evaluating the expression:
>#attributes.press_date#
>
>The strange thing is that the example I showed you now works, I
inadverantly
>fixed it yesterday without realizing it, I still have the error on a
>different fuseaction under the same index.cfm so formUrl2attributes is
>working fine, somehow or other the form variables are not making it though.
>I expect I will find a silly mistake in the next while here and come back
to
>the list full of humility :)
>
>-Shane
>
>
>-----Original Message-----
>From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, January 16, 2001 6:11 AM
>To: Fusebox
>Subject: RE: attributes.whatever not showing up when passing form
>variables to a sql query
>
>
>Shane,
>
>There are only two things that make sense.
>
>1) For whatever reason, <cf_formURLToAttributes>
>isn't included before that query (or perhaps all
>of your queries). In this case, you'll get an
>error something like "error resoving parameter."
>
>2) Something in your application is causing
>either the attributes or the form values to
>change. Since in the example you gave, everything
>is a text field, odds are this problem would
>not throw an error. But if this is the problem,
>you should get an ODBC error.
>
>I have a feeling that the fact that the broken
>code is in a query is just a coincidence. Look
>deeper. The problem most likely has nothing to
>do with the database.
>
>Patrick
>
>
> > -----Original Message-----
> > From: Shane Johnson [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, January 15, 2001 3:28 PM
> > To: Fusebox
> > Subject: attributes.whatever not showing up when passing form variables
> > to a sql query
> >
> >
> > Hey people,
> > I'm not sure why but, as stated in the subject, I am not
> > able to use attributes.formfieldname in my sql queries, I have to use
> > form.formfieldname. Is this a known phenom or is there a little
something
> > extra I should be doing, my app works fine ofcourse but I hate to
deviate
> > from the fusebox way of using "attributes". I am using attributes
> > throughout the application so they are working as per form2url
> > specs. I am
> > also using the code from the book to reuse the form for edit,new
> > and delete,
> > perhaps that is affecting things?
> >
> > This works...
> >
> > <cfquery name="updatepressrelease" datasource="#request.myDSN#">
> > update press
> > set
> > press_head = '#form.press_head#' ,
> > press_head2 = '#form.press_head2#' ,
> > press_body = '#form.press_body#'
> > where (index like '#pressindex#');
> > </cfquery>
> >
> > This doesn't
> >
> > <cfquery name="updatepressrelease" datasource="#request.myDSN#">
> > update press
> > set
> > press_head = '#attributes.press_head#' ,
> > press_head2 = '#attributes.press_head2#' ,
> > press_body = '#attributes.press_body#'
> > where (index like '#pressindex#');
> > </cfquery>
> >
> >
> >
> > Shane Johnson
> > Web Production/Programming
> > Populuxe Digital Media
> > www.populuxe.com
> > [EMAIL PROTECTED]
> > (604) 714-2496
> >
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
