In a theorhetical sense, Client/Server is about architecture, not implementation. In theory, you could set up an architecture, consisting entirely of VFP components, that would theorhretically be C/S.

Practically speaking however, is a different story. VFP's data engine is file server based, not client-server based. In terms of the benefits of what a client/server archite4cture can provide, you won't see them.

Bascially, take away the VFP data in favor of SQL-Server, Oracle, or some other C/S RDBMS, and you will be on your way....


>Without trying to justify why anyone would want to do this, I would like to understand the possibility of an all VFP client-server solution. I'm talking about a VFP server program using VFP tables and talking over a network to VFP clients. I'm assuming that the VFP server would maintain exclusive access to a set of VFP tables which would store the data for many clients. It would have little or no UI. The clients would use local cursors but would not maintain any permanent tables.
>
>1) Has anyone done this?
>
>
>2) What kind of data-transfer protocol would be used?
>
>2a) HTTP?
>
>2b) DCOM?
>
>2c) ??
>
>
>3) What kind of network would be required?
>
>3a) TCP/IP?
>
>3b) NT Server?
>
>3c) ??
>
>
>4) What else should I think about?
>
>
>Peter Robinson