>I just came to know that a third party tool for converting foxpro/dbase programs directly to VB is round the corner, will it spell doom for us (VFP), (***Pray Not***)
>
>Shashi


Code is code is code.

The strength of FoxPro (IMHO) (IMHO) (IMHO) is the data engine. Nothing on the market can touch FoxPro's accessing data against FoxPro tables. If your accessing databases other than FoxPro's, than it does not matter what development platform you use, the speed is basically same. There are other advantages to FoxPro but the Data Access is the greatest reason for using FoxPro (IMHO). This is In My Humble Opinion!!

I get into this discussion at the local MSDN meeting with VB programmers all the time. I ask them how they justify charging $5,000 ~ $6,000 for producing an application and then tell the client that "Oh, by the way you need to buy MS SQL Server for additional $1,200 ~ $1,500 for just a 5 user version of SQL Server." The VB programmers say that companies just need to spend the extra funds or use Access. I say, unless there is a business based reason for using a separate backend database, FoxPro is a better solution. Then I tell them to stick a couple of million records into a table over 1 gig in size and see what happens to an Access table.

The arguement over VB killing FoxPro or which is better is an acedemic arguement. Both products have their strengths and weaknesses. Both products are moving forward. We just need to say, "Yeah, right" when a VB person starts attacking FoxPro. After all, we know which product is Best! :> :> :>

This is IMHO again.