>I have been performing some tests accessing both Microsoft Jet databases and VFP 3.0 databases from in VB 5.0. I have seen the Jet/Access databases to be 50% faster at times. Also, when using DAO Dynasets in VB to view query results, I have seen the VB version run 10 times faster than the SELECT in FoxPro. With the ease of development provided by VB 5.0, extreme leanness, and now speed, what place is left for VFP?
>
>Has anyone had similar experiences? What are your impressions?

The Jet database is much slower when working on datasets over 10-20,000 records or so. It also doesn't support the array of transaction processing, buffering, triggers, and extendable data dictionary of VFP.

Also aside from the faster database VFP also boasts a true object oriented language. VB can not come close to VFP's ability to produce reusable business components and applications.

This is the primary reason that we use VFP rather than VB. The difference between OOP and non-OOP is night and day. Simply VFP has allowed our company to develop much better applications than we would have with VB. Unfortuantely learning how to develop reusable components takes months and years of practice. VFP developers are getting that experience while VB only developers are not.

For that reason the VFP developers I work with feel that when VB finally does get true OOP components, we will be poised to use those techniques. Current VB developers are not using OOP strategies and therefore will have to untrain themselves is structure/procedural programming. As any VFP developer who has learned to build true reusable components will tell you; this is not easy.