|
Query/400 might handle optimization at the time the query is created, but this is not going to help if you change the name of the file(s) and/or library the query will run upon.
I'm inclined to get away from Query/400 as much as possible. If you want the formatted report, use QM forms. STRQM is where you can manage these, and the interface is very much like Query/400. And the greater flexibility and functionality of the SQL you can put into QM queries is much greater than that of Query/400, IMO. The only thing Query/400 does more easily is summary-only reports, AFAIK.
If you want ad hoc queries, QM queries come to the rescue again - look in Google for EXCSQLSTM to download an example. There are some problems with this approach that can bite you in certain extremes and boundary conditions.
Embedded SQL has 2 kinds - static and dynamic - are you referring to dynamic, passing in the statement?
HTH Vern At 11:05 AM 12/21/2005, you wrote:
Are there any performance issues to consider when looking at embedded SQL versus Query400? It seems that Query400 might actually run faster, but I can definitely see the advantages of creating an SQL statement on the fly per se. Thoughts, comments? Tell me I'm nuts....ok skip the last one, that's a given. If you bought it, it was hauled by a truck - somewhere, sometime. -- 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 mailing list archive is Copyright 1997-2025 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.