RE: Need ideas for SQL join select to replace logical view

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: bill.blalock@xxxxxxxx
>
> I am trying to wrap my head around SQL.  This is a very basic problem in
> my inventory project ... matching the owner of an inventory item at the
> point in time with what happened to that item.  In this case the ownership
> of the item is one process (hence the owner file) and what happens to
> inventory is another process (hence the status file).

By the way, this is a very typical class of problem: trying to find records
within ranges based on other records.  Pricing (especially deals and
promotions) works very much on this sort of principal.  Other things work on
ranges and subtotals as well, such as batch balancing or production line
loading.

Partitioned tables in SQL can help with some of these problems but not all.
I just can't understand why someone would want to rewrite this stuff from
ISAM to SQL when ISAM works so much better.  If ISAM is the best tool, use
it. 

Joe