>Are you only including users in North America? I am betting that there are many more users out there than you might think. The majority no longer reside in the U.S.A.

- Attendance at VFP conferences in Germany and Prague aren't what they used to be. People there are looking at other tools.

>This is immaterial IF we get a true .Net compiler. Microsoft has stepped out of the ring.

Then it's not the core VFP product. In fact, it's not really VFP. It is a different product. Corporations will be somewhat resistant to it because it doesn't come from one of the big players.

What makes you think a .Net VFP app will be any easier to maintain than a VB or C# app in .Net?

>This assumes the current state of the software (No VFP Compiler for .Net).
>
>Incidentally Craig you still have not said, other than your above comment about the web, what it is that makes you believe that VFP is so inadequate.

Some of it depends on how we define our needs. If you defin your app to use DBFs, then DBFs are lacking security mechanisms. If you define your app to use SQL Server, then it's different.

VFP is COM-based and COM tools and components are dieing. It will become increasingly difficult to interop between applications with VFP. Even today there are issues with web services, which are supposed to be an easy way, but VFP only supports BasicHttp and none of the WS* standards that add tons of functionality.