Hi
If this is the trend, then VFP has a future, IMO, because its local data handling capabilities which is far superior to ADO .NET
I don't mind to have 100 smart clients VFP apps using a web service written using .NET :), but this is not going to happen.




>
>A web application in .NET (and even in VFP 8) can feature a distributed architecture with a 'smart-client' piece in Winforms that communicates with a .NET web service through XML, which can (in turn) work with the application/middle tier (either straight shot or through remoting). All wtihout HTML, JavaScript, etc.
>
>Granted, the end-users must be running the .NET framework, but it's still web-based, and is becoming increasingly popular as an architecture for corporations with many remote users/sales forces, with UI requirements that go beyond a browser's capabilities. It's also profoundly stated in tech papers on MSDN with titles like 'Death of the Browser'.
>
>Kevin