>A good point. Also, I don't know if the control has been revised lately, but here is another trap to watch out for: by default it does a LOCATE first, then a SEEK() - which if you are working on a big table can really bite you, timewise. You might watch out for that. <

LOCATE is optimized just like a seek, and in many cases it is preferable because it helps get away from the large number of compound indexes developers used to write in order to do a seek.


---Scott.