Government Solutions, Inc.
202-245-6484
[EMAIL PROTECTED]
-Original Message-
From: Bobby Hartsfield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 3:53 PM
To: CF-Talk
Subject: RE: Update: error emails firing for no reason (I still need
help)
I've never seen that happen before but I'm
Check your FORM tag along with any JS validation your doing.
Sometimes it can happen if you have a form tag that has:
OnSubmit:CheckForm() instead of: onSubmit=return CheckForm();
That way if the form validation false it would return false and NOT
process the form. Else might be doing it twice.
I've never seen that happen before but I'm sure it's caused by some bad code
(no offense) but without seeing some code, I doubt anyone can help unless
theyve seen the exact same thing happen.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus
Update: I have the cause for why this is happening. The
reason is that the form processing page is calling itself
mere seconds after it is first called. The second time
around, the form field do not exist, and that's the reason
for the error.
The problem is, there is nothing in the
As was mentioned, try another browser. Also you don't have any weird
programs like a web accelerator installed, do you?
Russ
-Original Message-
From: Barthle, Robert (Contractor) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 3:37 PM
To: CF-Talk
Subject: Update: error
I seem to remeber a colleague had a similar problem before (not 100% on this).
I believe it was to do with the company proxy. Try a pc at an offsite location
~|
Upgrade to Adobe ColdFusion MX7
Experience Flex 2 MX7 integration
Try using httplook and see if the traffic is really coming from your
browser.
Russ
-Original Message-
From: Richard Cooper [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 3:48 PM
To: CF-Talk
Subject: Re: Update: error emails firing for no reason (I still need help)
I
But anywhere from 1-3 seconds later, a GET request is sent from the
same IP address for the form submission page, and the listed referring
page is the forms processing page.
Would you have by any chance some onsubmit function that does a submit()
on the form?
That would cause the form to be
Well Judy it is just saying that it cannot find the form field. This means that
when you hit update, it is not passing the title variable to the next page. You
may have to put the title in a hidden field.
Success is a journey, not a destination!!
Doug Brown
- Original Message -
Please post the pertinent form html.
Jamie
On Thu, 18 Apr 2002 12:23:22 -0400, in cf-talk you wrote:
When I edit data in a form and click update, I get an error and cannot see why I'm
getting it. The field name is spelled correctly as it is in the database.
Error Diagnostic Information
An
[EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 12:38 PM
Subject: Re: update error
Please post the pertinent form html.
Jamie
On Thu, 18 Apr 2002 12:23:22 -0400, in cf-talk you wrote:
When I edit data in a form and click update, I get an error and cannot
see why
Jamie,
I just happened to think - are all these field names case sensitive when
referring to them? If so, that could be my problem
Judy
- Original Message -
From: Jamie Jackson [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 12:38 PM
Subject: Re: update
P.S. - looking at the debug information at the bottom of the page would show
you this very clearly and quickly.
-Original Message-
From: Judy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 18, 2002 12:03 PM
To: CF-Talk
Subject: Re: update error
Jamie,
I just happened to think
Judy,
In your form tag is Method set to POST? If not, then all the form
inputs are actually passed as URL parameters - not form parameters.
Mark
-Original Message-
From: Judy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 18, 2002 12:03 PM
To: CF-Talk
Subject: Re: update error
I just happened to think - are all these field names case
sensitive when referring to them? If so, that could be my
problem
No, they're not case-sensitive. Variables in CF are case-insensitive.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202)
Judy,
I just happened to think - are all these field names case sensitive when
referring to them? If so, that could be my problem
No CFs not particular about what cases you use in your variables.
tdinput type=text name=Title value=#GetEventtoUpdate.Title#
size=67 maxlength=255
Is there
Jackson [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 12:38 PM
Subject: Re: update error
Please post the pertinent form html.
Jamie
On Thu, 18 Apr 2002 12:23:22 -0400, in cf-talk you wrote:
When I edit data in a form and click update, I get an error and cannot
Yes, it is.
cfoutput query=GetEventtoUpdate
form action=updateaction.cfm method=post
input type=Hidden name=ID value=#ID#br
- Original Message -
From: Mark A. Kruger - CFG [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 1:11 PM
Subject: RE: update error
?
andy
-Original Message-
From: Judy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 18, 2002 12:56 PM
To: CF-Talk
Subject: Re: update error
Here's the form code in my updateform.cfm file.
cfquery name=GetEventtoUpdate datasource=Events
SELECT
Events.Title,
Events.InterDesc
Here's
Your error is with #valid# - you've got it setting above (as numeric) while
below you have it inserting as text '#valid#' = remove the '' marks and it
should work.
James
"You're a big man, but you're out of shape. I do this for a living, so
behave"
try replacing : cfif isdefined("valid")cfset valid=1cfelsecfset
valid=0/cfif
with: cfif isdefined("valid")cfset valid="Yes"cfelsecfset
valid="No"/cfif
or remove the single quotes in: valid='#valid#'
I'd start there.
~Simon
Simon Horwith
Certified ColdFusion Developer
Fig Leaf Software
Two things to check:
1) Are these vars passed in a URL? Do they need to be URLEncoded?
2) Are you entering a value into SQL that causes truncation? You don't
always get truncation errors specifically, because they can cause other
errors. Sometimes it's good to check.
--Dylan
- Original
maybe the "from" field, that is a reserved SQL word ?
Greets,
Gastón
-Mensaje original-
De: Jeremy Toevs [SMTP:[EMAIL PROTECTED]]
Enviado el: Jueves 9 de Noviembre de 2000 13:37
Para: CF-Talk
Asunto: Update Error
I recieved the following error and
From: "Jeremy Toevs" [EMAIL PROTECTED]
I recieved the following error and can not figure out how to fix it. My query
looks just like the rest of my other ones, but this one just doesn't seem to
work. Can you help me out?
===
Error Occurred While Processing
I think valid = '#valid#' needs to be changed, if it's a yes/no field
#Valid# should either be 0 or 1 without quotes or basically:
Valid=0
Valid=1
That should do it...
Gregory Harris
Web Developer
Stirling Bridge Group LLC
- Original Message -
From: "Jeremy Toevs" [EMAIL PROTECTED]
you don't need ticks around valid if it's a yes/no field.
chris olive, cio
cresco technologies
[EMAIL PROTECTED]
http://www.crescotech.com
-Original Message-
From: Jeremy Toevs [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 11:37 AM
To: CF-Talk
Subject: Update Error
I
doesn't it need a name for the query?
it would be helpful to know field typing.
is this a form update?
-Original Message-
From: Jeremy Toevs [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 10:37 AM
To: CF-Talk
Subject: Update Error
I recieved the following error and
How's bout giving us the post-parse SQL in the debug output?
J
On Thu, 09 Nov 2000 08:37:26 -0800, in cf-talk you wrote:
I recieved the following error and can not figure out how to fix it. My query looks
just like the rest of my other ones, but this one just doesn't seem to work. Can you
If your database is in Microsoft Access, I think that a yes/no field is
actually numeric, so you don't need the single quotes around #valid#. No=0
and Yes=1 or -1.
Lucy
From: "Jeremy Toevs" [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Subject: Update Error
Isn't FROM a reserved SQL word?
from='#from#',
Todd Ashworth
- Original Message -
From: "Simon Horwith" [EMAIL PROTECTED]
To: "CF-Talk" [EMAIL PROTECTED]
Sent: Thursday, November 09, 2000 12:45 PM
Subject: RE: Update Error
| try replacing : cfif isdefined
Access reads a yes/no field as a 1 or a zero. Take your quotes off and pass
a 1 for yes, or a zero for no. See if that helps.
-d
Deanna Schneider
Interactive Media Developer
UWEX Cooperative Extension Electronic Publishing Group
103
Or .. if you *must* use FROM for a field name, put it in " "
Todd Ashworth
| I recieved the following error and can not figure out how to fix it. My
| query looks just like the rest of my other ones, but this one just doesn't
| seem to work. Can you help me out?
|
|
-
From: Todd Ashworth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 2:30 PM
To: CF-Talk
Subject: Re: Update Error
Isn't FROM a reserved SQL word?
from='#from#',
Todd Ashworth
- Original Message -
From: "Simon Horwith" [EMAIL PROTECTED]
To: "CF-Talk&qu
You can't have a reserved SQL word as the name of a column and refer to it
like a normal column. In your query, you have from= '#from#'. FROM is a
reserved word. You will need to change the name of the column, or put ""
around it to let the database know what you are trying to do. This is in
34 matches
Mail list logo
