--You can not use EMPTY --
Thanks. You are correct. I just found it under the "Using Rushmore Query Optimzation to Speed Data Access" topic. I would think they would mention it in the EMPTY topic. Wouldn't that make sense?

I still contend if we can figure this out based on a set of rules then the engine should be able to figure it out based on the same set of rules. Isn't that what computers are supposed to be all about? Making it easier for us!



>>>That's just how engine works. I don't think there is anything wrong here as long as it is documented.
>>
>>I know that and I know it is not a bug. I just think it would be VERY nice if the engine could figure it out and optimize it. Or I guess in the help file topic for BETWEEN and EMPTY there could be a note something like "You shouldn't actually use these functions because they stink!"
>>
>
>You can not use EMPTY() (and AFAIK it's documented in Help) and you should use between with the field, not with a variable between two field values. That's all.