Dragan,

I seriously doubt that it does. The fastest thing VFP could do is use the raw internal representation of 32 bit integers directly. There's no reason to go through the gyrations of bintoc() while building a B+Tree. It would take a lot of time in a hex viewer to watch a CDX as values are inserted. I've read that FoxPro uses RunLength Encoding compression too which would make it harder to find key values.

>I think the basic story remains - VFP does use BinToC() internally to build integer keys. Gurus?