| pblais@odstrategies.org 2006-07-10, 9:55 pm |
| 1. First, use a VIEW. ABC Views in Clarion really are the magic you
can't live without. Best advice I would offer is think VIEW for all
Browse, Processes and Reports. Just use a VIEW all the time and you
are headed for faster apps.
2. Make filter strings on the fly and never BIND a local variable -
you should never need to do that so don't go there. BIND is a lazy
programmer tool. This is one time being lazy is bad.. But VIEW is a
good lazy programmer tool - you write less code and SV does the real
work for you.
3. If you do number 2 you can optimize the filter sting to reduce the
redundant code. Similarly don't project what you don't need and make
the filter string as short as possible. Using the driver trace you can
even optimize critical procedures more by studying the trace.
Clarion browses, processes, and reports work with a VIEW and a Clarion
VIEW is doing a lot of the heavy lifting for you. They flat out are
faster than hand code so many times it is foolish not to use them. You
really don't pay a penalty for using a view often enough to concern
yourself, Every time SV develop an enhancement you get it with no new
code written by you.
In hand code,I use Mike Hanson's SuperStuff for his roll your own VIEW
template - mhView. A perfect tool for source code with a VIEW. Views
require a little bit of hand code to feed the VIEW. The more you use
a VIEW the faster your apps will run and the good news is it works for
TPS and SQL both, but SQL can pay big dividends.
The ABC templates have a lot of power and VIEW to me is a really
important one. Use a VIEW and let the guys at Soft Velocity do the
hard work for you. Your LOOP's with SET, NEXT really are dog slow in
SQL. Lose your legacy bad habits when converting to SQL or you'll not
write faster code.
On 10 Jul 2006 10:39:54 -0400, Guest 6 wrote:
>Hopefully, though, some of you may have some
>personal observations or suggestions
---------------------------------------
Paul Blais - Hayes, Virginia
|