>It certainly is possible for valid businss cases to call for a rewrite, my point was not just that many rewrites are done without valid business cases, but that such a situation is extremely rare when the case is converting a VFP app to .Net. I have never seen a valid justification, and i doubt there could be one, although I certainly allow there could be a case I have not thought of nor seen.

You might want to read the conversation between Hamlet and Horatio :)

There are many instances where moving from VFP to .NET is based on business cases.

I worked on a vertical market application for years in the consumer packaged goods industry, where we needed to port from VFP to .NET/SQL Server over 10 years ago in order to even be considered for future contracts.

I've spoken with other vendors who have said the same thing - that they needed to get out of Fox (and out of other tools as well) and into larger platform areas in order to secure future work.

Additionally - I know of instances where company A purchased company B, where B had applications using products that A did not support. While in some cases Company A would "grandfather" those apps in, quite often company A would expect those apps to be rewritten. I know of one instance that specifically involved a Fox app.

And note my inclusion of SQL Server - a number of VFP to .NET conversions also had SQL Server (or Oracle) in the mix - in recognition that both are far superior in the database offerings area.

Think about this for a minute - much of the VFP talent pool from 15-20 years ago has moved on to combinations of .NET, SQL Server, Oracle, etc. If the statement "I have never seen a valid justification for a rewrite, and I doubt there could be one" truly held water, then many of the best and brightest wouldn't have had the need to move on.