>>>I did two projects using .net and VFP that worked out well. Recently, I was tasked to do another, but customer said .net was not approved for their network. So I switched to Web Connection for an all VFP solution. Now I'm doing my HTML in Notepad and rest is all VFP code. I like it better this way.
>>
>>While Notepad will certainly work you can continue to use the VS.Net HTML editor (which actually sucks big time!), FrontPage, Dreamweaver etc.
>>
>>My current favorite is FrontPage 2003 - it has a number of improvements that are the best of what Dreamweaver has and what FrontPage was good at including great publishing features that were a major PITA before in FrontPage.
>>
>>FP 2003 is in beta and can be gotten from Microsoft on CD. It's a big help to use somethhing like this even if you're using Web Connection and Templates/Scripts for HTML generation. In FP2003 this stuff works great visuall and in HTML display mode.
>
>In your samples provided with Web Connection is a DHTML example that allows a developer to create "windows-like" forms inside IE.
>The example are amazing....
>One can make an interface very similar to a desktop interface.
>
>Why wouldn't you lean on this method rather than HTML/Templates?
>Is there some kind of downfall in that these DHTML pages are as you term 'rendered' to the screen?
>Is there a 'negative' of doing pages as in your DHTML sample that I am missing ?

It only works in IE and there's a fair amount of overhead in rendering HTML from a running form. It's much, much slower than generating HTML in templates.

And frankly the Windows Forms style model just doesn't look right inside of the Web browser - almost like it's trying to hard to be like a Windows interface which a browser interface is not.

It works, and for some things it works well - I use it for many applications in the Admin interface...