So - I guess I still see a market here in the maritimes for the small networked application. Simpler, cheaper and easier to develop.

BUT, and this is a big BUT, if we are moving to a browser front end, then I believe this is *tremendously* liberating, for then we can use whatever tools we please, from whatever family of OS's, and deliver the appropriate results. I do see prblems in scenario's where you want on-form validations, subtotalling. etec. Can someone point to examples of these?

>>What I would *really* like to see in the next version [of VFP]
>>is databinding between VFP controls and ADO recordsets so
>>that we can offer solutions that use DBF solutions or
>>Desktop SQL Server (or --- what is it called now? ---
>>the MS Universal Database).
>
>This will be the true test as to whether Microsoft
>is going to support VFP in the long term. VB already
>has a databinding of controls to ADO. As companies
>over the next few years stop writing ODBC drivers
>for the newest and fastest databindings (OLE-DB),
>VFP might not even be able to easily access the data
>with remote views (if ADO databinding doesn't happen).