×
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.
Jim Essinger wrote:
I know that on my first 3 or 4 update, delete or insert statements, I could
have written a program to do the same thing in less time. However, now that
I have paid that learning curve time, I can do things much faster with an
SQL statement than by writing a program.
Just my 2 pennies.
Jim:
Since I agree, I put it at more than 2 pennies. As I said, I'd probably
do it with SQL myself. I've used SQL for more than 20 years, though, and
the problem was clear, as it was to those who supplied the multiple answers.
What made me think was how a debug session would have shown exactly what
the problem was in RPG. In SQL, you either already know the answer or
you start asking to see if someone else knows. Debug isn't quite the
same with SQL. You don't get to see what happens inside the SQL
statement as it runs.
Somehow, it seems like there should be a better way. As abstraction goes
to higher levels, things get harder to see.
Tom Liotta
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
