It all depends on your needs. How big will the app scale? What will happen when you physically separate the tiers? Will you need to interact with non-Fox components? BTW, binding objects to ADO is not that difficult. All Fox UI objects, except the grid, will bind to ADO. One problem with remote views is that you can't call stored procedures, which give you better performance and security.

>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.
>
>I guess I would still use VFP cursors w/ the ADO. For example,
>Retreive:
>SQL-Server -----> ADO recordeset -----> VFP cursor (easier to bound, etc.)
>
>Update:
>VFP cursor ------------> ADO Recordset ------------- SQL-Server
>
>Am I looking for unnecessary trouble if I use ADO rather then just keeping it simple?
>
>Any thoughts will be apppreciated.
>Thanks - Mark