× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have not tried this, but apparently you can create a view with an ordered subselect. Something like this is supposed to work:

CREATE VIEW ORDERED_CUSTOMER (ARBAL_CUST, ARBAL_BAL) AS SELECT joined.ARBAL_CUST, joined.ARBAL_BAL from
(SELECT ARBAL.CUST as ARBAL_CUST, ARBAL.BAL as ARBAL_BAL, (SELECT CUSNAME from CUST where ARBAL.CUST= CUST.CUST) as CUSNAME from ARBAL order by CUSNAME) AS joined;

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, April 22, 2013 12:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL index over field from another file

I don't believe this can be done the way you're wanting to.

The way I see it, you don't want to:
- use OPNQRYF (I'm cool with that).
- don't want to change the logic from RLA to imbedded sql
But you cannot create an index over two tables.
And a view cannot have an order by.

Back in the bad old days, third normal form might have been tossed out the
window and a column added which either had the customer name, or the first
so many characters thereof. On an existing table an effort may have been
undertaken to discover a column that was unused and repurpose that. Then
an add or change trigger would propagate this repurposed column with the
name (or abbreviation). Then build your index on that .


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.