Hi John,

>I think both places have their share of superficial discussions. Both places also have their fair share of solid technical discussions as well. I certainly don't think CIS is intellictually superior to the UT, nor do I think the converse is true. Both have their respective strengths and weaknesses...

Great! :)

>AFP to me is based on old methods. AFP is what West-Wind was 3+ years ago. Seriously, if you are going to go the AFP way, you might as well use a tool that does stuff like that well - Cold Fusion. AFP goes the way of emedding VFP code inline with HTML. To me, that is not very scaleable. Also, resuse is difficult, if not impossible. I think ASP/Components is the way to go... Just my opinion... I could be wrong...

Let me first clarify that I don't have many experiences with internet development, so if I say anything wrong, please correct me...

AFP works similar to ASP, except that you don't use VB Script. In an AFP page you can include the actual code, yes. But for scalable applications that's probably not the best choice. OTOH, you can also instantiate an MTS component that returns information via whatever you use in this case. I personally don't see much difference between an ASP and an AFP page, except that on the AFP page the code is more readable. :)

Christof
Sysop in MSDEVAPP