>>What I've been wondering about: How about Rushmore? Or more precisely, how about the typically superb performance when querying? Do you think you'll gonna need the LINQ facilities that are currently implemented? (I'm assuming here that database features in VB.NET will show a similar speed after the LINQ project has finished.)
>
>I maybe wrong about this, but isn't Rushmore all in the VFP index files?
>
>Pertti

To put it short, Rushmore is the name of the technology which optimizes the use of the available indexes.

From http://www.foxprohistory.org/rushmore.htm: Rushmore is a data access technique that permits sets of records to be accessed very efficiently. Rushmore query optimization uses indexes efficiently to quickly find a set of records. It is used on queries that involve restrictions on multiple-indexed fields. Rushmore is an exclusive technology for rapidly selecting sets of records from tables. It can reduce query response times from hours or minutes to seconds.

The legendary data access performance in FoxPro stems from its Rushmore query optimization and use of fixed length storage of data. Rushmore creates bit-mapped indexes that allow the engine to very quickly determine whether each row in a table meets a criteria and should therefore be included in a query's result set. Fixed width storage of data ensures that a field will be in the same location from row to row, making that field easier to locate.

Starting with the Rushmore query technology in the Visual FoxPro 2.0 release, FoxPro's primary attraction has been its fast data engine. It doesn't seem to have lost that edge over the years: posted reports on the newsgroups claim the new release of Visual FoxPro is twice as fast as SQL Server, for 50 users or less.