Do you think about n-tier client-server VFP application?

>I've had the thought for some time now that it would be a niche to create a Foxpro app that would function as a database server in the same fashion as a more traditional SQL database server might.
>
>Why try to make Fox behave as a SQL database server when there are already a multitude of products that do this?
>
>The answer lies in the file formats. Using a traditional SQL database product, access to the actual data files occurs primarily only through the engine itself. However, in the name of interoperability, I could envision situations when one might want to direct read-write interaction with the database table files.
>
>Besides, wouldn't it be neat to have a Foxpro "server" program execute on a server? Pass your parameters to a Foxpro program, let it execute on the server without passing data over the network. But let it still be a "regular Foxpro program" such as an FXP or EXE or whatever.
>
>In a really big corporate environment, it wouldn't be such a big deal. A large corporation could have an entire network subnet for transferring data between database servers, and in such cases, a "full-blown" SQL database system would be far and away the engine of choice.
>
>However, in these times, there are lots of small businesses trying to make do the best they can on their current network architecture. A full-blown SQL database might be out of the question. Foxpro has always been the database of choice in such cases BUT the primary issue is that Foxpro processes data on the workstation on which the program runs, not on the server where the data may reside. All data must be transferred over the network and queried or filtered or whatever, and this network traffic could reach debilitating levels and congest small networks.
>
>I am running Foxweb as a replacement for ASP. Somehow during the server installation when IIS was installed from the NT CD -- instead of the companion "option pack" CD in the same package -- we ended up with IIS version 3 instead of IIS version 4. We didn't discover this until the whole thing was installed, however, and the solution -- to uninstall IIS and reinstall -- was considered unacceptable. Foxweb was the solution, and we found it worked much faster than ASP and ODBC anyway. Watching Foxweb in operation is what gave me the idea for an actual database server process, written in Foxpro, which would execute and perform the majority of data mining operations on a server instead of littering the network with a lot of unnecessary traffic.
>
>How feasible would this be? Would it be worth the effort?