|
Home > Archive > IIS ASP > April 2006 > Posts from Form providing Bizzare Results
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Posts from Form providing Bizzare Results
|
|
|
| I'm using the POST method to submit a simple form html page with yes/no
and checkbox fields to an asp response page which stores the values in
a new dim string, then uses it to build a new table using ADO. I'm
getting sometimes correct values, sometimes null values (when I know I
pass a valid default value) and other times multiple values! I know
what the values coming over are because I do a response.write to see it
before the error appears. The errors that I get are multistep value
errors or more commonly data type value errors. For example, a field is
set with a 0 for No, or a 1 for Yes is supposed to send a "0" by
default. In some fields it does, in others it sends a null value, still
others it sends a "0,1". Both values!
There are no hidden fields in the form.
Has anyone seen this bizarre behavior and/or know what may be causing
it? I'm stumped.
| |
| Mike Brind 2006-04-27, 7:51 am |
|
Billy wrote:
> I'm using the POST method to submit a simple form html page with yes/no
> and checkbox fields to an asp response page which stores the values in
> a new dim string, then uses it to build a new table using ADO. I'm
> getting sometimes correct values, sometimes null values (when I know I
> pass a valid default value) and other times multiple values! I know
> what the values coming over are because I do a response.write to see it
> before the error appears. The errors that I get are multistep value
> errors or more commonly data type value errors. For example, a field is
> set with a 0 for No, or a 1 for Yes is supposed to send a "0" by
> default. In some fields it does, in others it sends a null value, still
> others it sends a "0,1". Both values!
>
> There are no hidden fields in the form.
>
> Has anyone seen this bizarre behavior and/or know what may be causing
> it? I'm stumped.
It would be useful to see the html of your form. That way some us might
be able to replicate your problem or identify errors in it. Without
that, we are only guessing.
--
Mike Brind
|
|
|
|
|