> Maybe I'm missing something, but I can't think of any possible use for a
> query that returns results like this. It is only of use when using
> serialized storage, such as files, and wanting to read from a certain point
> in the file to the end. But there still isn't anything useful in the results
> once the initial starting company is processed, unless it is date based and
> you are relying on everything after a certain point to be dated later. (I'm
> pretty sure that's not the reason, though.)
>
>

Doesn't matter. The point is that it needs to emulate ISAM file
behaviour. Just because that doesn't make sense in the example that I
gave doesn't mean it doesn't make sense in other situations. I am
looking for a general solution, not one that needs to be hand crafted
based on what makes sense in each particular case.

>
> The simplest way to duplicate (still don't know why anyone would want to)
>

That's because you don't think like someone who has used nothing but
ISAM files for 30 years. Believe me, it is a different world.

> what they have now, IMO, would be to use a floating point field as the
> primary key. That way you could find the starting point and retrieve
> everything with a higher key value. Adding information would simply be a
> process of finding where you want it inserted and dividing the sum of the
> two key (previous and next record) values by 2.
>

You definition of simple and mine vary considerably. Besides, that
still doesn't address the need to be able to access the data using the
values that make up the key.




[Non-text portions of this message have been removed]