×
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.
It would be helpful to see the full SQL statement which caused this error.
Perhaps if you qualified your field names in the SELECT statement by using
the filename or a correlation name you probably would not get this error, or
you would have discovered it the first time that you tried executing it...
Example:
Select A.Field1, A.Field2, B.Field3 from FileA A
join FileB B on A.Field1 = B.Field1
- sjl
Jeff wrote:
Hi All,
I just got bitten by this error today:
Message . . . . : JOIN predicate not valid.
Cause . . . . . : The JOIN predicate is not valid because a column is
specified that exists in a table that is outside the scope of the
join predicate.
The scope is generally determined from left to right but is
also based on the position of the join-condition. If parentheses are
used, columns inside the parentheses can not come from a table outside
the parentheses.
Recovery . . . : Do one of the following and try the request again:
-- Make certain that the column names, table names, and any qualifiers
are specified correctly.
-- Specify parentheses around joined tables to specify a join order
other than left to right. Ensure columns exist in tables that are in the
same scope.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
