John,
Thanks for the tip. Validation did find some errors, but even after I
fixed them it didn't work.
But by trial and error (after getting some sleep! :) ) I discovered
the offending jQuery line. With the upgrade, I had the wrong syntax
for the name attribute. In trying to fix it, I found some funky answer
on the web last night which apparently caused the problem. But this
morning I found the right answer (i.e., $("input[name='dept']").click
(function() { etc etc...) and the problem's solved.
Thanks again for your time. I don't know if you get tired of hearing
it (hopefully not!) but jQuery ROCKS! I'm just learning it, but it has
simplified my coding and put wonderful enhancements within easy reach.
THANK YOU!!!
Kathryn
On Mar 30, 10:16 pm, John Resig <jere...@gmail.com> wrote:
> Well, without being able to see the form in question - does your page
> validate? If everything is going into a single input that sounds like
> a problem with malformed HTML markup.
>
> --John
>
> 2009/3/30 Kathryn <kathry...@gmail.com>:
>
>
>
> > I'm working on a web form and had to upgrade to 1.3.2 tonight to solve
> > some problems. Unfortunately, I now have a much worse problem. Not by
> > my choice, I have to use ASP. With the lower version of jQuery, the
> > form was working fine and I could process it as usual...e.g.,
>
> > HTML:
> > <input name = "dept">
> > <input name = "employee">
> > etc. (There are around 40 fields on this form)
>
> > ASP:
> > dim dept, employee
> > dept = request.form("dept")
> > employee = request.form("employee")
> > etc.
>
> > However, since upgrading, when I submit the form and response.write
> > the results on the ASP page, the contents of ALL form fields are
> > contained in the dept variable and all the other variables are empty.
> > I know it's not a problem with the ASP code, because it was working
> > immediately before the upgrade and I haven't changed it.
>
> > Has anyone else had this happen, and if so, what did you do about it?
>
> > Thanks in advance,
>
> > Kathryn
