>I am rewriting an existing vfp application that uses native fox tables. In the re-write, SQL-Server will be used as the backend.
>
>I have used VFP remote views for c/s apps and am fine with that technique.
>
>I believe we will have an easier time creating a web-based app in the future if I begin this project using a middle-tier w/ ADO.
>However, I am not sure how much time using ADO w/ VFP, rather than remote views, will add to the project.
>

Here are some other considerations:

- With WebConnection, you can use cursors directly to build HTML pages. Of course, it provides a lot more functionality as well.
- You might want to research the similarities/differences between ADO and ADO.NET. Will the work you do now with ADO be supported in ADO.NET?
- Of the frameworks available, COMCodeBook probably provides the best support for using ADO.
- Although converting between ADO recordsets and cursors is possible, it's not perfect. I think most of the recommendations will be to use one or the other. That's not to say you shouldn't support both, (ie. VFP front end uses cursors, ASP uses ADO), just avoid the conversions.