No it won't. It will Modulo the 2000427 by 10000 and go directly after
427.

What you have to avoid is using 64-bit E and R keys. If whole number
values are used, you get a degenerate key where the whole base has one
primary and everything else secondaries. The reason is that only the 1st
32 bits are used for the hash and for whole numbers between 0 and 4mln,
the 1st 32 bits are the same.

Shawn Gordon wrote:
>
> An I doesn't hash, which is why it's faster, it goes to the physical
> location represented by the value.  If you control them and sequentially
> assign them, then it is fast, however... If you are using date as an
> integer key for example and have a capacity of 10,000 and a value of
> 2000427 in the key field, then image is going to loop around until it
> counts up to 2,000,427.
>
> You are typically better off with an X
>
> At 03:23 PM 4/27/2000 -0600, Timothy Hoefner wrote:
> >I'm going at it again with our DBA but I can swear that I learned
> >somewhere that TurboImage can hash faster with an X item
> >rather than an I item.
> >
> >I hope I made sense.  Thanks again.
> >
> >
> >Timothy J. Hoefner
> >[log in to unmask]
> >(915) 831-6144