If it can be re-written so as to incor****ate some independent intermediate
queries, do so until each is running smoothly. Then add them back in, one
at
a time. You may find that you gain some speed if you don't add everything
back in.
Another thing I do is to put long clauses into #DEFINE's and/or macro
subs.
This lets me hide some of the complexity while debugging.
"Gene Wirchenko" <genew@[EMAIL PROTECTED]
> wrote in message
news:o1nrm3dfulbe7g56mj01d9j5uml3vd8mdp@[EMAIL PROTECTED]
> I have just finished -- I hope I have finished -- some changes to
> one program of mine that has some hairy SQL. One of the SQL statments
> is 40 lines long. Granted it could be shorter vertically, but it is
> still 852 characters long.
>
> Occasionally -- read "All too often" -- while wrestling with this
> program, there would be an error in my SQL syntax. VFP is not
> terribly helpful with such error messages as
> Syntax error.
> Command is missing required clause.
> These are not terribly useful. Sometimes, I have hunted for minutes
> before realising that, say, a comma was missing.
>
> What do you do to quickly find errors in long SQL statements?
>
> Sincerely,
>
> Gene Wirchenko
>
> Computerese Irregular Verb Conjugation:
> I have preferences.
> You have biases.
> He/She has prejudices.
|
