Steven & Judah, thanks! I guess I'll change those fields into properties- I hate "breaking style". The class is sealed- it's basically for some help during a system data migration- but as trivial as it is, I don't want any poor coding habits popping up! -Thomas

Yep, that was the problem. Just had to right-click "references" in the project window, and say "Add"! -Thomas

So nobody has any idea... or opinions, or even Guesses? Nobody uses response.redirect here? I thought for sure that someone would. Or did I make my question too technical? If I did, let me know, and I'll rephrase it. Thanks! -Thomas

ThomasH1 wrote: my test server will be what it was when I was running VS6.0 Sometimes the old ways are best.:-D "Your village called - They're missing their idiot."

ThomasH1 wrote: My Big Question is: What's the equivilant of my old COM component in Visual Studio .NET 2003?? Okay, I know I'm replying to myself, but I think I might've found what I was looking for. It was above a link in the MSDN docs that jdunlap pointed me to. Link is http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconexposingnetframeworkcomponentstocom.asp , "Developing Components". The docs are written for VB & VC# (figures), but I think I can apply it to MC++. One bit jumps out at me, under the "Class vs Component vs Control" section, under the Container & Site heading. It says "If you are developing components...for Web Forms pages (ASP.NET pages), you do not have to implement containers or sites". I've got more reading to do, but can I assume that ASP will take care of threading? Thanks! -Thomas