>In reading through the dicussions about C\S vs File Server and how it relates to network traffic. I started thinking about Web servers and with VFP backends residing on the same machine. The data is never sent to client, it only goes to the Web server. How does this senario impact network traffic?

VFP is excellent for this, because it is lightning fast when accessing native data. After the web app converts the data to html/xml or whatever, relatively little needs to go over the wire, so performance is unbeatable.

It falls in a "true" client/server architecture though, when the client is doing the querying, because VFP is not really a server database, and is not optimize for that kind of use. It's ODBC driver is really pretty lame, and not practical for any large scale C/S deployment.

>What are the concurrency issues?

Could you be more specific?

>VFP seems like a excellent datasource for Internet apps.

I agree.