>>>Hi,
>>>
>>>I have rewritten my VFP 9 application completely using CursorAdapter approach and I like it a lot. (Create a BIZ object for each table of the database, drop it on a form, and then change or add records/rows via the BIZ object; works very well. The BIZ object is based on CursorAdapter).
>>>
>>>And I am wondering; if I wanted to use the same type of approach for an ASP.NET application, what would be the closest to VFP CursorAdapter in .NET world? TIA.
>>
>Still with a VFP back-end for data ?
>
>Update : just saw your similar post in ASP.NET so see that it will be SQL backend.
>
>I'll vote with Craig for EF on this one. If, as you say, your application is simple then the EF wizard should get you up and running quickly. You can either point it at existing DataTables or design the objects (model) and let it create the tables for you. And what you learn will give you a head-start if you need EF to handle more complex issues down the line......
>
>Not particulary recommending EF over nHibernate (which I've never used in anger) but certainly prefer it to working directly with DataTables and/or TableAdapers. I'll refrain from listing the reasons unless you are interested.....

First, to your initial question, yes, still VFP back-end. It took me a long while to convert my VFP app to work with SQL Server (just installed first beta copy on a customer site). The ASP.NET has to work with whatever database is used by the Windows (VFP) application. Hence my ASP.NET uses VFP. After this change, I will make the ASP.NET work with either VFP or SQL Server.

As far as EF, of course would like to know why "in anger" and would appreciate if you list the reasons.

Thank you.