> I don't actually think it is this complicated.
> as you use it with normal clientside HTML controls. There
> are however a few caveats.
> If the name of a server side event clashes with the name
> of the client side event this will lead to a problem.
> a webform button control you will need to use the
> onMousedown client side event rather than the onclick
> event as the there is an event named onclick on the server
> You will have no intellisense when you write the
> controls do not actually exist till they are rendered as
> HTML when the application executes.
> Also when referencing the control reference it as
> doent.all rather than doent.Form1, I have sometimes
> had problems with the latter syntax.
> Pat Sinnott MCSD
> >-----Original Message-----
> client as
> >scripting embedded in the HTML of a page. Therefore, you
> cannot interact
> however, add
> when the page loads
> >in the browser. You can do this by using the
> >Page.RegisterClientScriptBlock() and
> Page.RegisterStartupScript() methods.
> >Kevin Spencer
> >Microsoft FrontPage MVP
> >Internet Developer
> >Some things just happen.
> >Everything else occurs.
> >"Krishna" <gk_ananthhotmail.com> wrote in message
> >> Hi all,
> controls.Any appropriate
> >> site which will be tell more on this will be helpfull.
> >> Regards..,
> >> Krishna