× 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.



Here's a simple example.  You've got a MASTER file that has IDs, names, and
a spouse's ID# that is also in the file.  If you link T01.MASTER to
T02.MASTER using the spouses ID, you can get both entities names into a
single record.  This used to work very well if you have a gender code ;-)

HTH

Joe

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CWilt@xxxxxxxxxxxx
Sent: Wednesday, February 25, 2004 7:40 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: A query about Query

It's a pretty common practice.

All you are doing is linking rows to other rows in the same table.  Usually
pretty obvious why this technique needs to be used.

Though I must admit, I'm having trouble coming up with an example <grin>.

If you still have questions, post your query and will tell you why it's
doing it.

Charles


> -----Original Message-----
> From: Kincer, Alan [mailto:akincer@xxxxxxxxx]
> Sent: Tuesday, February 24, 2004 5:05 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: A query about Query
> 
> 
> Some the file selections of my more "advanced" queries 
> contain two entries
> of identical files. In the record selects I will see where a 
> field form the
> "T01" of the file would be searched against where another 
> field of, say, the
> "T02" version of the same file would be included. Can anyone 
> tell me what
> the purpose of this practice would be?
> 
> Thanks,
> 
> Alan
> 
> 
> 
> === [ KI (USA) Corporation - http://www.kiusa.com ]
> ====================================== 
> Tel. 859.986.1420  --  Fax. 859.986.1485 
> This e-mail, including any attachments, contains information 
> from KI (USA)
> Corporation that may be confidential or privileged. Mail is 
> intended only
> for those to whom it is addressed. If you are not the 
> intended recipient do
> not copy, distribute, or take any action in reliance on the 
> contents of this
> message. 
> If you have received this e-mail in error notify the sender 
> immediately then
> delete or destroy all electronic and hard copies of this 
> communication,
> including attachments. 
> KI (USA) Corporation's anti-virus system checks for known 
> viruses. However
> you are advised to run your own virus check before opening 
> any attachments
> received. KI (USA) Corporation will not accept any liability 
> once an e-mail
> and/or any attachment is received. 
> Views expressed in the e-mail are those of the author and not 
> necessarily
> those of KI (USA) Corporation. 
> ==============================================================
> ==============
> 
> 
> _______________________________________________
> 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.
> 
_______________________________________________
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.