×
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.
LF is a weird bastardization of VIEW and INDEX. It really is an INDEX as the only thing stored in it is key fields and pointers (ODP) but there's potential record selectivity, column selectivity, and even table joins embodied in the LF which are totally foreign to an INDEX. INDEX and VIEW separate the data path from the selectivity.
VIEW's can reference tables and other VIEW's. VIEW's cannot reference INDEX's, but the query engine will use INDEX's as it sees fit to produce the results efficiently. It is the INDEX quality of LF that precludes reference from within the VIEW. The query engine MAY use the ODP from an INDEX when it resolves a VIEW.
So, in your VIEW, reference the TABLE that the LF is built over. Let the query engine do its thing to use LF's if it can.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crystal Reports
Sent: Wednesday, May 29, 2013 6:39 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Views and Inner join
Can you do an inner join on Views? Also it seems you cannot use a Logical in Views.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
