request.form(i) is there a 'name' property?

[JulianUK]

Hi

Is there a 'name' property (or the like) when using Request.Form(index)?

i.e. i need to get the name of a particular element by it's index, rather than by it's name. The reason being that I'm iterating through all form elements, but want to ignore those of a certain name.

It's got me stumped anyway.

Many thanks and have a great Christmas.

Julian

 

[Sheco]

if you had the following code in an ASP:
[tt]
For Each Foo in Request.Form
Response.Write Foo & " = " & Request.Form(Foo) & " <br>"
Next
[/tt]

it would print a list of all of the request elements and their values...


So by extrapolating a little, we can do what you ask like this:[tt]
For Each Foo in Request.Form
If Foo = "BadValue" Then
Response.Write "We skipped one!<br>"
Else
Response.Write Foo & " = " & Request.Form(Foo) & " <br>"
End if
Next
[/tt]

... just use your own "BadValue" ...

 

[DotNetGnat]

<%
For x = 1 to Request.Form.Count
Response.Write Request.Form.Key(x) & " = "
Response.Write Request.Form.Item(x) & "<br>"
Next
%>

-DNG

 

[JulianUK]

Thanks Sheco, but that wouldn't suit. I'd be checking data values, and for all I know, one of the values I don't know could be "BadValue". Hence I need the actual name of the item.

DNG, exactly what I'm after, and exactly what I found out a few minutes after I posted, but I couldn't post back for some unknown reason, an error with the forum.

Cheers though, and IS there a good online reference for that sort of thing?

Julian

 

[damber]

JulianUK,

Sheco's example has the same result as DNG's - except with a bit of validation for the name you want to omit. In Sheco's example, Foo would be the name of the value which is then used as the key to the collection. DNG just posted a variant of Shecos approach, which rather than using the named index of the collection gained from iterating using For Each, it uses the numerical index gained from a For incrementor loop.

Hope that clarifies.

Good References for learning ASP:

http://www.w3schools.com/

http://www.devguru.com/

http://www.aspfaq.com/

http://www.asp101.com/

There are many more, but the best one is:

http://www.google.com/

;-)




A smile is worth a thousand kind words. So smile, it's easy!

 

[damber]

JulianUK,

Sheco's example has the same result as DNG's - except with a bit of validation for the name you want to omit. In Sheco's example, Foo would be the name of the value which is then used as the key to the collection. DNG just posted a variant of Shecos approach, which rather than using the named index of the collection gained from iterating using For Each, it uses the numerical index gained from a For incrementor loop.

Hope that clarifies.

Good References for learning ASP:

http://www.w3schools.com/

http://www.devguru.com/

http://www.aspfaq.com/

http://www.asp101.com/

There are many more, but the best one is:

http://www.google.com/

;-)


A smile is worth a thousand kind words. So smile, it's easy!

 

[damber]

What IS going on with the site today... ? Posting is almost Random...

A smile is worth a thousand kind words. So smile, it's easy!

 

[DotNetGnat]

damber...even if you are bored that doesnt mean you have to post it multiple times ...

just kidding...i noticed that the submit button on the site is having some problems...

-DNG

 

[damber]

Hey.. twice the post, twice the help....



A smile is worth a thousand kind words. So smile, it's easy!

 

[JulianUK]

Thanks damber - right, without trying it I wouldn't have realised that - thanks for explaining.

and thanks for the links!

 

[JulianUK]

PS. Therefore, thanks Sheco, I apologise!

 

[JulianUK]

Hhmmm. maybe I wouldn't want to use the "for each..." method afterall. Seems the fields may not appear in the original order using this method.

http://www.4guysfromrolla.com/ASPScripts/PrintFAQ.asp?FAQID=64

unfortunately this is fundamental to my processing logic. I think I'll use a mixture of both.

both methods are great. I wish i'd known about it a while ago instead of coding around something I never needed to!

 

[damber]

the fields wont necessarily appear in the expected order in any case.. you are reliant on the browser sending them in the order you wish, which is not gauranteed, especially in different browsers, however the link above is correct in that it is more CONSISTENT to use direct indexing to access the array.

A smile is worth a thousand kind words. So smile, it's easy!

 

[JulianUK]

oh boy is nothing ever simple?!

Thanks.

 

[damber]

Where would the fun be if it was..?

A smile is worth a thousand kind words. So smile, it's easy!

 

[Sheco]

If you require the form elements to always be in a certain order perhaps you could name them in such a way as to allow you to extrapolate the order.

So that your form elements look something like this:
<input type="text" name="box_1">
<input type="text" name="box_2">
<input type="text" name="box_3">