David,

>> it's highly unlikely this ad-hoc indexing is an part of rushmore.
>
>This statement is not true. If you've ever issued a SELECT statement and the thermometer bar doesn't appear for a significant period of time FoxPro is building the temporary indexes it wants to use to give the rest of the select optimal performance.

I know the SELECT command is using temporaty indices, as I said before in this same thread, but since these kind of indices are only used in a multitable SQL SELECT query and not in other rushmore optimizable commands it looks to me that this feature is a part of the SQL SELECT optimizing mechanism rather than a part of rushmore.

The foxPro (2.5) developers guide, page D17-2:

'FoxPro's SQL facility makes use of Rushmore as a basic tool in multi-table optimization, using Rushmore with existing indexes and even new ad-hoc indexes to speed queries'

In this statement I can't see that the ad-hoc indexing feature is a part of rushmore, only that rushmore is using these ad-hoc indices (genereated by the SQL optimizer ?). Besides this this statement seems to say that rushmore is not the only tool used in query optimization.

Walter,