Michel,

Agreed. Whether to upsize to SQL Server is not a "selection of development tool" issue.

If you are doing a web service that does not require your own software at the client pc, that removes much of the dotNET scalability risk I mentioned earlier.

Presumably you are proposing tiered development? If so, and if VFP is doing some sort of "munging" before passing data back to the .NET presentation layer, or if there is already proven functionality in existing VFP classes, you can easily argue why it is rational to make use of that.

However, if VFP is simply retriving data, one might reasonably question why you wouldn't "keep it simple, stupid" and use dotNET for the middle tier as well.

Needless to say, some would advocate using Stored Procedures directly from the presentation layer, in which case .NET is all you need.

I'm assuming you are proposing VFP because it can do something especially well?

Regards

j.R