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



Pete

RTVQMQRY has these known limitations - only type 1 queries are correctly converted.

Charles suggested looking at the JOIN spec in WRKQRY - I forget the rules about the joins, but they are documented - I too wish for a complete and useful converter.

Vern

At 08:01 AM 10/12/2007, you wrote:

"Pete, make sure you double check the joins being done in query vs. the
joins being done in SQL. "

There's the rub. I don't know what the joins are in the query because
all I have is a list of "where " comparisons. That is I have "Where
field1=field2 and field1 = field2 " etc instead of "from file1 join
file2 on field1= field2 join file3 on field1 = field3" That is what is
leaving me scratching on head on a " Matched Records with Primary File"
option in query. There are no joins listed in the query from RTVQMQRY.

I guess to restate this: If there WAS a way to see the exact syntax (SQL
Syntax) from a query, replicating that in SQL would be a snap. As it
is, when you have a complex query that produces the desired results in
Query/400, you basically have to start from scratch in rebuild that
query in SQL. In my particular case I have a query that outputs in a
way I expect in Query/400 but replicating that same result in SQL had
been devilishly difficult.

I wonder how the new Web Query product is going to migrate existing
Query/400 queries (if it indeed does do that)? They must have a better
tool than RTVQMQRY .

Pete


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.