Erik,

I saw the statements the same as you. Someone took the sales brochures and cut and pasted.

PF

>Here's my take.
>
>>ADP - Access 2000 is now fully integrated with SQL Server through a new feature called Access Data Projects (ADP). Previously you had to use linked tables, SQL pass-through queries, or ODBC directly to communicate with the SQL Server backend. With ADP developers have direct access to SQL Server tables from within the Access environment. Access 2000 can also directly work with Microsoft's new database engine MSDE 1.0 (which is actually SQL Sever core without the user interface) through ADP. However in our opinion, the Jet Engine (MDB files) is still efficient for localized processing of smaller subsets of large data. The only disadvantage of using Access ADP is that your backend will have to be SQL Server or MSDE. You cannot use it for Oracle or Sybase backends.
>
>Recommending one product over another by talking only about the features one product without referencing the other is non-sequitur... These new features of Access are great, really, but what's the point? Is this a comparison or an Access sales line? I could write pages talking about great VFP features, but without comparing them to Access, this is meaningless to the argument.
>
>
>>FAMILIARITY - Since your developers are familiar with Access 2000, you can minimize training and hiring costs by continuing to work with Access. Although some of our work has been in FoxPro, we are more knowledgable about using Access to develop frontends to SQL Server.
>
>This is a good reason, but only applicable in certain circumstances. If it will be a sizable project, the cost of training or consulting to do the work in VFP might very well overcome the extra development time that will be required to write the project in Access.
>
>>COST - Access development is also more economic. Since it more widely used than Visual FoxPro, tools, resources, and help is more easily available for Access. The cost can be dramatically lower if you are building a system where Access is going to work with its native database.
>
>This is hogwash. There is absolutely no lack of online support for VFP, as is evident here.
>
>
>>However, there are few advantages of using FoxPro which do not directly impact why Access should be used over FoxPro in working with SQL Sever/MSDE. Unlike Access, FoxPro is a true Client/Server system.
>
>Ok.
>
>>FoxPro can be used to create both the frontend and the backend in a high performance Client/Server solution.
>
>NItpick- if Foxpro is used to build the backend and the front end, its not really C/S, but I will give him high-performance.
>
>>Visual FoxPro also comes with its own object oriented programming language which is specially useful when a large number of programmers are cooperating on the same project.
>
>I think this is significantly underplaying the advantages of OO. Any medium to large sized system can benefit from the use of VFP's OO features, multi-developer or not.
>
>>FoxPro also offers Active Documents which can be hosted by Active Document Containers like the Internet Explorer.
>
>At least he has read the sales literature, but that sounds like all he's done. Anyone with internet experience in VFP knows that AD is a dead end.
>
>
>This is all just my opinion. I could be wrong.