Yup definitely tgreer.
I'm sure I'll be back with more problems lol.
But thanks for the prompt replies

Thanks for the gracious answer... I thought my last post came across too strong. My point was, ASP.NET is a profoundly different web development methodology (profoundly flawed, in my opinion).

Thus web developers who understand the client-server nature of the web, the stateless environment, etc. who then try to switch to ASP.NET, which "pretends" that you're developing on a fat client with state, will have a very difficult time.

We get tripped on on KNOWING how the web works, what the client does with scripts, cookies, and the retinue of HTML Form elements and CSS. ASP.NET hides all of that from the developer, so we end up fighting it all the way. Your scenario was a perfect example: you wanted to create some HTML elements, client-side, with JavaScript. You then wanted to get those values, server-side. Simple, in ASP or PHP - mind-numbingly awkward in ASP.NET.

Nah... tend to learn better with truthful words

Btw, yup what you said is true. I used to be a Coldfusion developer, am still one. The reason I've got to move on to ASP.net for this particular project is because ASP.net is free. I got to have this program deployed client-site and they will use it locally. So I could not use CF in any circumstances

I'm so used to CF that I'm starting to miss it while developing in ASP.net lol.
Thanks again tgreer
Will be checking frequently on the board hoping to learn as much as possible