>>Business needs seem to change from year to year. I imagine that most systems >>require some maintenance from time to time. Thus, I still think that is a >>consideration that many managers must make--where will I find new talent to >>maintain the system in the future.

If you're looking for the tool that has the best capabilities for maintainance, VFP lays far ahead of VB because of the OOP.

>>VFP does not support full ANSI SQL, which I would like to see. I should have >>been more clear concerning VB and SQL; I meant to say that it provides more >>direct access to SQL Server available to the developer aside from ODBC. In >>fact, MS promotes VB as optimized as a Client/Server front end for SQL Server >>and Oracle. I have only seen VFP pushed as a middle tier (and this only >>through VFP links) and as a reporting tool for C/S.

True, VFP does not support the full ANSI SQL version 2 (SQL 92) standard, but VB does not support any SQL at all. VFP does however support great c/s capabilities which are far more advanced than the JET databases. Btw VFP support flexible replication through the off-line view. you can alway's make use off ODBC to take advantage of the complete ANSI SQL set.

I regard VB as a programming language which is easy to learn. That's why VB is used by so many "developers". Much of them are really amateurs. VFP is not pushed by MS because it's a professional programming tool (which does not have to be pushed because the return of investment (of the marketing) is much lower compared to a tool which was intended as a end-users tool) by the way has MS J++, C++ pushed lately? I'm convinced that the average VFP-programmer stands on a much higher level than the average VB "programmer" (Certainly concerned about OOP).

>>I hope I have clarified this. I would like to see MS do more in these areas, >>but I doubt that they will. Gates definitely has two products that compete >>against one another. By the way, why did MS not push to have VFP included as >>Client/Server development tool in a comparison of VB, Delphi, and >>Powerbuilder? VFP is definitely a peer of these tools...

The difference bewteen VFP and VB are:
- VFP is OOP , VB is not. (and will not be, as clarified by MS)
- VFP is possintioned as a database Tool, VB is a general purpose tool.
- VFP supports the stongest (and fastest) local database currenlty arround.
- JET is for small bussines applications

as for ACCES,
- ACCES is for ease of use for end users (ACCES is included in MS Office)
- VFP is for professional developers (Included in Visual Tools)