>Also I Am trying to convince the rest of this commitie to dump VB and go with VFP Any Valid amunition would be helpful
>

What problems are U experiencing with VB? VB combined with a powerful back-end data engine is a worthy tool. VFP can be used to go against other ODBC compliant data engines. I really depends upon your needs. Do you need a client/server environment? Will there be more than one person performing data entry? What are your transaction processing requirements? Does the company have a standard? Do any other legacy system exist in VB at this company? Maybe U should consider the big picture before choosing a development tool. Perform a needs asssesment and offer your client more than one alternative. There are other tools out there, each with individual strong points. In addition to VB and VFP consider Delphi and Access also.

Personally, I push VFP when possible or if the client has no preference. U should be able to justify using VFP by discussing the RAD environment and data access speed (a'la Rushmore). My biggest selling feature is that I will train end-users in MS Access Query and genreal SQL so anyone can analyze data and create customized reports. My VFP users love creating there own little SQL programs. Well htwh...