>For the Edit type screens, I might use Macromedia HomeSite to generate the initial HTML then I would manually insert the VFP field identifications.

VS.NET lets you edit your pages visually, dropping server controls on the form and writing code behind the. If you're not familiar with Web Forms, check this out, its a brief introduction, but it should give you a feel for whats possible.

http://www.levelextreme.com/Magazine/March2002/Page9.asp

>For Tables, I would write my own HTML code to set up the TABLEBORDER, CELLPADDING etc. then I would insert VFP Scan ... EndScan code in between. Where input is permitted into the tables, there are some pretty elaborate code requirements to get the new data back to the Web Server.

For lists, you drop a DataList or DataGrid control on your Web Form, set some formatting properties, and then do something like this:

MyList.DataSource = DS.Tables("Table").DefaultView
MyList.DataBind()

This will automatically populate your control from an ADO.NET table.

ASP.NET Web Forms ease the page creation process considerablly. THere's a 17 year old student working for me with no programming experience at all, and he got a functional ASP.NET pages working after an hour or two of playing and following the Quick Guides.