D
darrel
This is a follow-up to a question I had yesterday.
Quick summary: our intranet server dies a month or so ago and we had to get
a new one up and running quickly.
Any .net app that ran on the old server was moved over. The catch is that
any of the apps that used client-side validation no longer properly
post-back. And we're not sure why.
In some further testing, I've found that the validation works, but the
postback never happens. So the page is never submitted and, as such, makes
for a rather useless application.
The fix is to turn of javascript and let the validation happen client-side,
but we're stumped as to why this happened.
The proper .js file that .net uses for validation IS being linked to (in IE)
and the file DOES exist on the server.
We're stumped. BTW, these same apps work just fine on our localhost or other
test servers.
-Darrel
Quick summary: our intranet server dies a month or so ago and we had to get
a new one up and running quickly.
Any .net app that ran on the old server was moved over. The catch is that
any of the apps that used client-side validation no longer properly
post-back. And we're not sure why.
In some further testing, I've found that the validation works, but the
postback never happens. So the page is never submitted and, as such, makes
for a rather useless application.
The fix is to turn of javascript and let the validation happen client-side,
but we're stumped as to why this happened.
The proper .js file that .net uses for validation IS being linked to (in IE)
and the file DOES exist on the server.
We're stumped. BTW, these same apps work just fine on our localhost or other
test servers.
-Darrel