Jim,

In a file-server architecture, a data file is opened over the network by multiple host applications with persistent connection, which do not only implement presentation, but also are data processing engines. This approach is a no-go anymore in enterpise soltuons of any scale. It was dominated in the past by fox/dbase/clipper systems. Fox was used as a database and as a client.

In a client-server architecture, a persistent connection still exists in most cases, but the database engine is centrally located and is exclusively responsible for data processing. A client is a "fat-GUI" application, which requires hard-deployment, bound to a specific language and not open for integration with the rest of IT components. This approach implies a transatiional/relational database for a data-tier (SQLServer, Oracle, etc, but not the Fox!), and "fat-GUI" client - VFP, VB, PB, Delphi etc.

In a web-based service-oriented architeture, data tier survives from client/server implementation - it is still transactional/relational database, but its role is more focused on only data processing, rather then on security/emaling/notifications and and other auxilary services. Clients are all thin-clients with really zero deployment (not ActiveX, not J-applets!) - all with universal presentation implementation - HTML. Clients connect to middle-tier services, with no persistent connection to databases. Middle-tier components could be anything - VFP COMs, PHP, ASP, ASP.NET, .NET assemblies, Java beans, etc. Components use HTTP to communicate between each other and most frequently encapculate data in XML for data exchange. There are no limits in how components are integrated or re-integrated using general purpose integration layer - web portal.

As for the small/medium enterpises, web-based service-oriented architeture is a forward-looking technology, and if you want to stay competitive - go for it.

VFP has everything (I mean the data manipulation part, not the database part) you need to implement solutions like these and beat PHP and Java in their own game :)

The exeption for the next few years could only be personal productivity tools, like word processor, spreadsheets, small database solutions, single-user accounting s/w - well this is where VFP could still be used. But this does not drive the technological advancement and the industry.