That sounds like a better solution for DB scalability. Then it should be easy to justify a VFP component if you have to like "we already have this done" or "because of the strength and proven reliability in this area" we're using VFP here..
Also, I remember someone was going to do an article in UT mag about a similar project (vfp/asp.net)they did along with scalability numbers. I've been looking forward to that - is that still in the works??

>>In this case, I would minimize emphasizing VFP (although use it heavily!) and use it as a middle tier ASP.NET component. This way it seems like more of a mainstream MS solution...
>
>The way I see it, it'll probably end up with SQL Server on the backend, on a dedicated server, and probably some adjustments in the process as far as the components go.