> evaluate is generally considered a security risk and is also slower
yeah, a while ago there were a fair number of blog posts highlighting this.
> form["hdnPersPBA_"&X] and structkeyexists
or simply (and neater)
form["hdnPersPBA_#X#"]
the point about looping over this list *is* a better way,
evaluate is generally considered a security risk and is also slower
On Mon, May 5, 2008 at 10:45 AM, Matthew <[EMAIL PROTECTED]> wrote:
>
> Why do you say that Zac?
>
>
> >
>
--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
--~--~-~--~~~---~
Why do you say that Zac?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
it's better to use struct notation, avoid evaluate if you can...
form["hdnPersPBA_"&X] and structkeyexists
z.
On Mon, May 5, 2008 at 10:13 AM, Matthew <[EMAIL PROTECTED]> wrote:
>
> Hi Barry,
> I use a similar method to what Kevan has suggested.
> On the original form page I have a hidden fo
Hi Barry,
I use a similar method to what Kevan has suggested.
On the original form page I have a hidden form element which stores a
list of all the form names which I want to look over on the "action"
page. It works a treat. All you have to do is as you're building the
original form page you dynam
> Not sure you need this any more
I'm always up for learning better ways, so your ideas/help aren't
wasted (thanx). Besides, finishing at 3:00am this morning gives me the
nagging feeling I'll be doing a Schwarzenegger [1]
> In your original form add another field called something like
> "hdn
Barry
Not sure you need this any more (re your moving on comment), but another
idea for you:
In your original form add another field called something like
"hdnPersPBA_fields" (and perhaps "selPersTit_fields") which contains a
dynamically built list of the fields you need:
"hdnPersPBA_1,hdnPersP
What about
Cheers
Gareth.
barry.b wrote:
> yeah, you're right - that was one of the choices.
>
> (FYI - there is a caveat there: there's a bunch of reserved suffixes
> that won't show up in FORM.fieldnames ... _date and _time are a
> couple)
>
> I was going to look at form.fieldnames as a li
Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of barry.b
Sent: Friday, 2 May 2008 12:43 PM
To: cfaussie
Subject: [cfaussie] Re: is there a more effic
9015 8628
Mobile: 0404 998 273
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of barry.b
Sent: Friday, 2 May 2008 12:33 PM
To: cfaussie
Subject: [cfaussie] Re: is there a more efficent way of finding keys in FORM
scope?
yeah, you're right -
> (FYI - there is a caveat there: there's a bunch of reserved suffixes
> that won't show up in FORM.fieldnames ... _date and _time are a
> couple)
found it: it doesn't apply to my case here but it's perhaps worth
remembering:
http://livedocs.adobe.com/coldfusion/6.1/htmldocs/format28.htm
--~--
yeah, you're right - that was one of the choices.
(FYI - there is a caveat there: there's a bunch of reserved suffixes
that won't show up in FORM.fieldnames ... _date and _time are a
couple)
I was going to look at form.fieldnames as a list to search but I
really need ListFind() to either return
Barry,
However there is one thing you can do. It won't change the outcome in
anyway. But Coldfusion gives you this.
Form.fieldnames
It is a list of all the fields, so you might write this instead, and notice
you no longer need to check the length anymore. Not sure why you had that
there to be h
13 matches
Mail list logo
