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 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 dynamically create a string which you keep
> appending all the form field names to. Then you just shove this string
> into your hidden field. This means that on the "action" page you just
> loop through the list stored in the hidden field. You obviously have
> to write validation code in case you are dealing with checkboxes
> (because checkboxes wont be Defined if un-checked). The brilliance of
> this solution is that when you loop through that hidden field list you
> can be confident that you created all those fields on the previous
> page, where as with your current solution you are looping
> unnecessarily and doing a lot of guess work.
> Buy the way; to use this solution you'll need to familiarise yourself
> with the Evaluate() and DE functions for usage on the "action" page to
> test and extract the values from these dynamically named field names
> e.g. Evaluate("form.hdnPersPBA_"&X).
> Hope this helps!
> Cheers
> Matthew
>
>
>
> On May 3, 12:47 pm, "Barry Beattie" <[EMAIL PROTECTED]> wrote:
> > > 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
> > > "hdnPersPBA_fields" (and perhaps "selPersTit_fields") which contains a
> > > dynamically built list of the fields you need:
> >
> > > "hdnPersPBA_1,hdnPersPBA_2,...,hdnPersPBA_n"
> >
> > > Then when the form is posted, you have a known set of fields to extract
> from
> > > the form scope.
> >
> > u mean: keep a record of what was created ( via the JS that's used to
> > clone new form elements and inject them into the DOM) and submit that
> > list as "hdnPersPBA_fields.value"? Yeah, that'd work, although I'd
> > also have to remove them from that list when the user hits the "I
> > don't want those new text boxes anymore" buttons.
> >
> > [1] ...http://en.wikipedia.org/wiki/I'll_be_back
> >
>
--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---
