Francois Lepoutre recommended Delphi as an alternative to VFP. From my perspective please note the following. Moving to Delphi seems like such a logical thing to do until your realize the diadvantages of a true compiler re database applications and come face to face with the sad but true fact that even with its compiled speed Delphi's data handling capabilities leave much to be desired. Writing classes and components is much more difficult than with VFP. The hugh array of available third party products leads to the temptation to constantly be acquiring the latest and greatest.There is no such thing as a macro in Delphi. There are no native dynamic arrays in Delphi. Arrays elements must be of the same type unless variants (slow) are used.If you use the BDE you are stuck with either dBase with HUGH single file indexes or Paradox with HUGH multiple file indexes as well as the quirky behavior of the BDE in general. Multi user programs can get completely screwed up if the BDE is not configured properly. If you use an addon database component you will lose some of the native capabilities of Delphi - most probably data buffering. Delphi will pop screens up much faster than VFP and on a low end machine it performs wonderfully. Try indexing a 100,000 record table and you will see that Fox is at least 3 times faster. Then there is the Pascal language itself. In many ways it is very similiar to FoxPro - except I find myself continually forgetting to put 'begin' and 'end' in the proper places. The subsequent code looks right and does not generate compiler errors but it doesn't do what your want it to. Then again, the business community if very leary of Borland or whatever they are calling themselves now. All in all, Delphi is a superior product but from the prospective of a FoxPro developer I believe that moving to it in essense is jumping out of the frying pan into the fire.