Re: SQL logical file equivalent

Why was needed to foot the bill? Key fields in the logical so that you
could use "traditional" or "Record Level Access (RLA)" with some HLL like
RPG (using keys other than what you'd use as a primary key)? Then, yes,
you're pretty much stuck with DDS. However, if you are using imbedded sql
to access the data, then I'd be hard pressed to find a situation where
you'd "need" DDS. And I keep trying to think of something that would work
better with RLA for something that would need an access plan different
than primary key. For example, a customer name lookup. Traditional is
primary key on customer number and a logical on customer name (or some
stupid alpha lookup field). However SQL, especially with it's powerful
SOUNDEX function would be a far better choice for name lookup's. Then
adding an SQL index on the name might help performance but a logical
wouldn't be needed.

Another example. order header and order detail. Sure, RLA based on order
number might not be bad. But adding a DDS logical on the order detail so
that you can the open lines by item number using RLA? No. I might add an
index on active record id, item number, order number, and query the file
using sql instead of RLA.

These kind of lookups, or reports, are more suited for the SQL approach
than the RLA approach.

Rob Berendt