>Jim,

>As was discussed here already, you really should go to an MSDN roadshow, or dotnet user group, and ask around.
>
>People are doing these apps, quite successfully. It's the people here who say it can't be done. But I guarantee you that there are many who are doing what you currently believe can't be done.

Ehh, twisting of words again. There are certain types of applications that can be done more efficiently in VFP, just because of disadvantages in .NET. There are people having performance and scalability problems just with .NET.

And sure there are thing you cannot do at the detailed level in .NET. You can't do SQL on ADO.Net locally, period.

BTW, You can do everything in assembly you like, but it does not mean that it is the programming language of choice.

Also, I have no clue what you mean with 'People are doing these apps, quite successfully'? Have you any idea what kind of apps we are talking about? Sure no-one would denie you could do database apps. But it really depends on what you are doing with it. It does not make sense to develop a .NET app for straightforward enterprise integration. You have ERP/ERM systems, that get cheaper by the minute doing that more efficiently for you. Then we might talk about specific requirements that might do simple database access and .NET merely provides the GUI to provide editing the data. Sure no problem also.

However, when we talk about highly data intensive applications, such as some complex (scientifical) management systems, you might get a total different picture. I've got a few applications data takes a small amount of data from a dozen tables and make huge calculations as output. There is a lot of data munging going on here. VFP simply is better equipped for doing that.

Walter,