> Get rid of the "*" in the SELECT *
Ben,
That did the trick. Thank you!
Nicholas Vacek
Vivid Image - Programmer
320-587-8974 ext. 111
[EMAIL PROTECTED]
http://www.vimm.com
Ben Nadel wrote:
> Get rid of the "*" in the SELECT *. Using CFQueryParam causes the
> structure to be cached. Then, if
Could the error be caused by scoping issues for the variables you using
in the CFC?
What scope is the variable "value" in, and is your cfif really
evaluating the Boolean "true", or is it a real cfif with a variable in
there? If so, what scope is it in? Arguments? Variables? Local Scope
(var)?
What happens if you change the variable name used to populate the
value attribute of CFQUERYPARAM?
If that fixes it, my money would be on a variable leak in the CFIF
implementation.
cheers,
barneyb
On Nov 26, 2007 12:58 PM, Nicholas Vacek <[EMAIL PROTECTED]> wrote:
> Can anybody help me figure o
>>What's going on?!?
>>either in your code or some system code
IMHO it is more like in the "system code" ;-/
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address: [EMAIL PROTEC
This is all I can think of... assuming you literally are using the
boolean true and not some real code evaluation...
AND fieldName =
The thought behind this is that CF is mis interpreting true to be a
variable name and not a boolean...
=]
--
Alan Rother
Adobe Certified Advanced ColdFusion
Get rid of the "*" in the SELECT *. Using CFQueryParam causes the
structure to be cached. Then, if the underlying DB changes, the
structure no longer applies, but since CF sees it as the same thing,
weirdness ensues. In general get rid of all SELECT *'s in your code.
They are evil and cause headach
6 matches
Mail list logo