>>>Even if you don't have a business layer, a DataSet is essentially a cursor (or a group of them if you prefer). The other important piece is the DataAdapter, which sits between the DataSet and the database. It handles the DB-specific stuff. The GUI and the rest of the front end of the app can work with the DataSet without knowing or caring where the data actually resides.
>>
>>Sounds like deacent n-tier aproach. But we had those in Fox since forever did'nt we ?
>>
>>What we also had is choice weather to use ready-made stuff, build entire thing from scratch, use or not use it at all, and get by occasion with ugly grid entry form that took less then a minute to build. Although this is one of those things that actually plagued Fox, I would newer let go off that possibility.
>>
>>I might start working with NET on certain projects, but I would never stop using FOX , for that freedom of choice alone.
>
>You can do all that stuff in .NET also.
>
>I can use the ready-made stuff (DataSets/DataAdapters), build it from scratch (Custom Objects/DataReaders), and get by with ugly grid entry forms (using the designer to hook everything up).

Okay. That got me convinced!

To try NOLOH {g}