On the 2003 server do you have the ASP_NET client? (usually this is your web
root/aspnet_client folder). Is the server running the same version of the
framework as you developed in? You should have a
root/aspnet_client/system_web/"frameworkversionfolder" like 1_0_3705_0 and
1_1_4322... make sure those are there.
It's important to realize that if your validators do not fire CLIENT SIDE,
they can still be caught SERVER SIDE, as long as you are checking if
Page.IsValid. Like:
If Page.IsValid then
'do my code
else
'exit sub
end if
This will fire your validators server side and the user will see it on
postback. Remember, not all browsers are going to support client side
validation, and if it's important, you need to check it again at the server.
-MCD
" Jason Shohet" <as****@hotmail.com> wrote in message
news:%2******************@TK2MSFTNGP10.phx.gbl...
They are working fine on our w2k servers.
On the remote site -- using 2003 server -- the controls don't occur until
after the action is taken. We are doing a catch, so that we don't give
the user an ugly error screen -- and we notice that the validators display an
error messgage there. I want to tell them,
"HEY, validate BEFORE the update / insert to the database, not
afterwards!"
In other words, the validator is not preventing the code from executing
when the submit button is pressed.
But again, it is only on that 1 server. Any ideas?
Jason Shohet