> > Correct. cmd.exe simply opens the window which allows you to run
> > batch files ... that's what CFEXECUTE is already doing for you.
>
> That's not correct at all. Batch files are run by the command
> processor - cmd.exe. CFEXECUTE is not a command processor.
I think you're misinterpreting
I converted all the statesments to this format and they ran
fine...they
did utilize the cmd.exe even though the cmd.exe wasn't explicitly called
with the format below.
The format seemed to work either way.
The issue I was having embarassingly was that when I rewrote the profiles
for Navicat
> Correct. cmd.exe simply opens the window which allows you to run batch files
> ... that's
> what CFEXECUTE is already doing for you.
That's not correct at all. Batch files are run by the command
processor - cmd.exe. CFEXECUTE is not a command processor. And in my
experience with CFEXECUTE, I'
I know for vb scripts you have to run cscript.exe and pass the path to the
vbs in the arguments.
--
Ryan
On Sat, May 23, 2009 at 8:43 PM, Jason Fisher wrote:
>
> Correct. cmd.exe simply opens the window which allows you to run batch
> files ... that's what CFEXECUTE is already doing for you.
Correct. cmd.exe simply opens the window which allows you to run batch files
... that's what CFEXECUTE is already doing for you. So just run this:
>Execute the batch file directly, rather than trying to go via cmd.exe ?
~
Execute the batch file directly, rather than trying to go via cmd.exe ?
~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
http://www.houseoffusion.c
You'd have to escape them or change the outer quotes to single quotes of
course. :)
--
Ryan
On Sat, May 23, 2009 at 7:03 PM, Ryan Letulle wrote:
> You might try putting the f:\inetpub ... in double quotes.
> --
> Ryan
>
>
>
>
> On Sat, May 23, 2009 at 6:27 PM, Rick Faircloth
> wrote:
>
>>
>>
You might try putting the f:\inetpub ... in double quotes.
--
Ryan
On Sat, May 23, 2009 at 6:27 PM, Rick Faircloth wrote:
>
> I can run this code, and see cmd.exe open in the list of services in the
> Task Manager,
> but cmd.exe closes rather quickly and there are no results from the batch
> f
I can run this code, and see cmd.exe open in the list of services in the
Task Manager,
but cmd.exe closes rather quickly and there are no results from the batch
file.
Just wondering if anyone sees any problem with the code, itself. This was
running fine
on XP, but now I'm executing it on Windows
uotes within the form field data. It would seem in this case that
manually escaping them would be pointless.
- Andy
> -Original Message-
> From: Philip Arnold - ASP [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 2:46 PM
> To: CF-Talk
> Subject: RE: see a pr
: 401.965.3661
E-MAIL: [EMAIL PROTECTED]
Web Page: www.creatcomp.com
-Original Message-
From: Peter Benoit [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 2:01 PM
To: CF-Talk
Subject: RE: see a problem with this code?
How about the comma after this line? comments = '#Form.com
> I have a pre-filled form for users to change a record.
> The form calls an action page to update the record.
> I keep getting the dreaded error:
Another problem you might run into is apostrophies in your fields - if
someone enters one in their entries, then your SQL will spit
I'd personally c
> I have looked backward and forward, checked spelling,
> quotes, etc., and can't figure out the problem. I
> figureed it was time for a new set of eyes. Is there
> something about this that I am missing:
> comments = '#Form.comments#',
> WHERE ID = #Form.ID#
Remove the trailing comma before y
You have an extra comma after the '#form.comments#', just prior to the WHERE
clause.
DC
- Original Message -
From: "Tim" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 13:50
Subject: see a problem with t
Not sure how you may have this worked out but,
maybe #Form.conf_date# needs single quotes as well?
RO
>-Original Message-
>From: Tim [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 28, 2001 12:50 PM
>To: CF-Talk
>Subject: see a problem with this code?
>
>
>
t;[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 1:50 PM
Subject: see a problem with this code?
> I have a pre-filled form for users to change a record.
> The form calls an action page to update the record.
> I keep getting the drea
Your last line should not contain a comma
comments = '#Form.comments#',
The comma represents there is another field
that is following.
-Original Message-
From: Tim [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 1:50 PM
To: CF-Talk
Subject: see a problem with
How about the comma after this line? comments = '#Form.comments#',
don't think it should be there... though I'm kinda new at this stuff. :)
-Original Message-
From: Tim [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 1:50 PM
To: CF-Talk
Subject: see a pr
there is a comma after the last item (comments) before the where clause,
don't know if this is a typo or a true problem
-Original Message-
From: Tim [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 12:50 PM
To: CF-Talk
Subject: see a problem with this code?
I have
Take out the last , on your set (comments = '#form.comments#')
HTH
Dan
>
> UPDATE data
> SET
> conf_name = '#Form.conf_name#',
> conf_purpose = '#Form.conf_purpose#',
> conf_date = #Form.conf_date#,
> occurance = '#Form.occurance#',
> begin_time = '#Form.begin_time#',
> end_time = '#Form.en
ginal Message-
|From: Tim [mailto:[EMAIL PROTECTED]]
|Sent: Wednesday, March 28, 2001 1:50 PM
|To: CF-Talk
|Subject: see a problem with this code?
|
|
|I have a pre-filled form for users to change a record.
| The form calls an action page to update the record.
|I keep getting the dreaded error:
|
|
the last comma
Tim <[EMAIL PROTECTED]> wrote:
I have a pre-filled form for users to change a record.
The form calls an action page to update the record.
I keep getting the dreaded error:
Error Diagnostic Information
ODBC Error Code = 37000 (Syntax error or access
violation)
[Microsoft][ODBC Mi
I have a pre-filled form for users to change a record.
The form calls an action page to update the record.
I keep getting the dreaded error:
Error Diagnostic Information
ODBC Error Code = 37000 (Syntax error or access
violation)
[Microsoft][ODBC Microsoft Access Driver] Syntax error
in UPDATE s
23 matches
Mail list logo