Wes, other things to keep in mind are backward compatability and VFP's history.
Backward compatability will not be an issue for new projects but nice to know that the VFP development team makes it work. Not sure the same can be said for VB (compare VB3 to VB6 - does VB3 code work under VB6?).

FoxBase/FoxPro/VFP has been around since around 1985 or 15 years. While this does create some baggage, it also gives ample time to work out bugs and provide a rich feature set. Compare the number of functions available in VFP to almost any other language. VFP has been an OOP language since version 3 or 1995. VB will get this in the next release.

I can't recall the last time I wrote an app that did not access a data store.
VFP is a data centric language. It does a great job working with local or remote data. I personally have a VFP table of over 12 million rows and it provides me with sub-second retrieval times.

Hope this helps with your decision. Good luck!

>Thanks for the input. The database I will be building in the near future will probably not excede 100,000 records per table. But I think I am still leaning toward Visual FoxPro for the simple fact that I may need the power of FoxPro down the road and I have to start sometime. The feedback I have received has informed me about all the speed and relighability that Visual FoxPro has. I guess the faster the better.
>
>Thanks,
>Wes Brown