No, that doesn't make much sense to me. The only thing I can guess is there may be some kind of problem with the data. Maybe there's a complex index expression that Rushmore is trying to use. You could try adding NOOPTIMIZE to the command. It will be really slow, but you'll know if Rushmore is causing that problem or not.


It was my mistake, I have chosen for the test a flat table with 254 fields.

Okay, It works in foxpro 8.0 and I understand the query. Thank you very much for your effort, help and also for your book suggestion, I'll have a look at it.


Zakaria al Azhar