Hi, Gerald,

Just got a reply from Jordan saying that developing in Dot Net reduces speed by a factor of about 5+. I.e. If it takes 2 seconds to query/save a file in VFP, it would take 10 seconds in Dot Net.

This would be definitely unacceptable.

If this is the case (I realise some folks experiences will be different), then I would need to very seriously consider any immediate move to dot net from VFP until Microsoft sort this out !!

I copied Jordan on this. I saw his post about development time being 2-3 times more and app speed being 5-8 times slower. I'm going to ask him to qualify/provide specifics on these numbers. I've been involved in multiple VFP->.NET conversions, and we don't have any users complaining about differences in speed or lost functionality.

As I said yesterday, much of the learning curve in .NET is about building a knowledge base to become productive. I've been working in .NET for 3 years now - and generally speaking, am about as productive in .NET as I am in VFP.

And by the way, just like with a VB application, or a C application, in a .NET database app you'll need to be running a back-end database, like SQL Server, Oracle, or even MySQL, etc. If a user runs a report where the query against the shared/networked VFP database takes two seconds, the same report for the same user running against a SQL database under the same general configuration (remote user/internal user,etc.) is not likely to take 10 seconds.

Kevin