Hi Kevin

In your experience of developing and comparing VFP and Dot Net, if you take the 'Fastest ' pssible way of doing things in Dot Net, what is the likely speed comparison for doing normal mundane things like:

1. Displaying a screen , with say no Grid
2. Displaying a screen with 2 tabs, Details and Grid, with say 30 transactions out of a table of 30,000 being selected into the grid
3. Running a query (for reporting purposes) which takes say 30 transactions out of a 30,000 record table


Would you say , in General, Things were about the same speed,twice as slow, 4 times as slow or greater.

I'm just looking for indications here.
You may think I'm very finnicky here, but in my experience, if response times are not sufficient, the app is thrown out. We recently went through a migration form FP 2.6 to VFP, and even though delays were only in seconds compared to FP2.6, there was fierce opposition from the users, even though they were getting a whole pile more in functionality and ease of use !!

If we were to upgrade one of our apps in Dot Net, say invest 2 man years in it, and then find that response times were remarkably slower, that invsetment would be down the drain and we would go out of business.

This doed'nt mean we necessarily would have to stay with VFP either. If it turns out that Dot Net is that slow, we may need to look at Java or someting else


Regards,

Gerard







>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