>>The server code that does this is quite simple.
>
>That's VFP code you are talking about, right?

Yup. In classes subclassed from Rick's WC framework.

>>But IMHO, this implementation does not a client server database make. You would still have to build connectivity into another development platform, include an XML parser, and unless the dev platform was able to bind to XML datasets, you would have to have another data format to convert to so you could bind controls. Either that or manually build ADO recordsets. (You can just imagine how blazingly slow that would be.)
>
>>A client server data should subscribe to some standard (usually ODBC) that allows it to be easily access from heterogeneous clients.
>
>This is where you lose me. If I can build a VFP server which can talk to a VFP client anywhere on the LAN or to an HTML browser anywhere on the Internet, isn't that enough? What other development platform should I be concerned about?
>What other clients besides VFP and a browser should I be concerned about?


I guess to me, C/S means means front end or back end can be swapped out without a hassle. And I gues you can build a PB client for my server, but not without a lot of work, and it would certainly be easier to just use an ODBC datasource.