Brett_A wrote on 19 apr 2008 in microsoft.public.inetserver.asp.general:
Quote:
Quote:
>Seems very clientside to me!
>Classic ASP does not know of forms
>nor of dynamically changing formfields.
Again: [please do not quote signatures on usenet]
Quote:
This is what you answered:
>
If this is a serverside code problem, show your code,
if it is clientside code or a html Q, ask elsewhere.
[wrong quoting level]
Quote:
If you read my question, why would you ask if I had a code problem?
Because that is the main subject of this NG,
and you did not include such problem.
Quote:
I hadn't gotten that fair in the development.
Ah, so you were just fishing? "that fair"? I think not sofar.
Quote:
After reading the other
answers and doing more research, it is partially client-side issue - I
think I need some AJAX to create the desired functionality.
Indeed. Ajax is in fact clientside coding technology,
as the requested html streamlayout from the server could be,
but not necessarily has to be,
prepared by serverside coding,
which coding even then is not part of AJAX technology as such.
Quote:
I was
asking the initial question to see where I should start - the last
sentence was "Any suggestions"? If you thought it was a client side
issue, why not answer like Bob did? It was informative without being
condescending.
So that is the bottom line:
You are asking and at the same time think
you have a right to determine how the response should be?
While it was not my intention to be condescending,
[you could be from the west side of the great pond,
where such sensitivities excessively abound,
as seen from the rest of cyberworld,]
it won't do to expect the absence of condescence on usenet.
Quote:
"Any suggestions"?
So again, show us the serverside problem, and do some initial work
yourself, and you have a good chance of getting help where you get stuck.
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)