Sorry, you were looking for the EFFICIENCY difference between the two methods, not the actual values that would be included in them?
My guess is that, because the BETWEEN...AND is a single set of comparison factors and the >=...<= is a double set of comparison factors, the BETWEEN...AND would be more efficient.
Nanoseconds! Who knew they could add up so fast? ;-)
It's very difficult to get information about how Jet works. Having been brought up on things like DB2 I find this frustrating. You get snippets on the Microsoft site but no complete picture.
Personally I wouldn't have thought there was any difference. I would assume Access would translate BETWEEN into >=/<= before it scanned the index or data pages.
I would guess, and it's only a guess, that BETWEEN ... AND would be more efficient (if there's any difference) because it could be be optimized better than the separate >=, <= which could be any two conditions and which would have to be treated in a more general way.
[blue]_____________________________________________________
If you need immediate assistance, please raise your hand.
If you are outside of Raleigh, raise your hand and say[/blue] [red]Ooh! Ooh![/red]
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.