×
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.
"Main point -- Why the view which is created on a physical file(physical
file which itself is created by joining two or more files like i shared
in my last post with SQL queries examples) shows much more records than
the file(file1 in my SQL queries examples 1.,2.,3,,4.)"
Doesn't matter how the PF was created. The consensus of those who have
commented here is that:
1) SQL on a view created over a PF
and
2) SQL on the PF using the same criteria you used to create the view
should give the same results.
If not then you must have an error (maybe a typo) in the SQL creating
the view or in the SQL using the view. But since you won't or can't show
the code, then there is no help we can give.
On another front, I don't know how QRY/400 will treat a view as input,
which is why I pointed you to the "Define result fields" approach for
verification. if you are required to verify with QRY/400.
"Also how would IBM i ACS be superior to traditional STRSQL here , I
mean what I can't do in STRSQL can do using IBM i ACS here?"
STRSQL is old and it is difficult to make changes to what you've keyed.
And easy to pick the wrong SQL when you go back to the history. That's
why I suggest you delete everything and start again.
With iACS you have the benefit of a GUI editor and is easier to change
code, you can easily save and reload code to files on your PC or on the
IBM i. It can have multiple panes open, each with a separate SQL
statement. It can also reformat code. And it has a lot of examples. It
leaves STRSQL in the dust.
But to each his own...
>On 7/4/2022 7:56 AM, jerry ven wrote:
Also how would IBM i ACS be superior to traditional STRSQL here , I mean
what I can't do in STRSQL can do using IBM i ACS here?
Main point -- Why the view which is created on a physical file( physical
file which itself is created by joining two or more files like i shared in
my last post with SQL queries examples) shows much more records than the
file(file1 in my SQL queries examples 1.,2.,3,,4.)
is there a difference in a Physical file which is traditionally created by
midrange.com
