Gene -
I take a different approach.
I programmatically build SQL Select statements,
and run each piece of it (select, into, where, join, etc)
through a sql pre-processor util that i built some time ago.
i have different flavours of it now, for native vfp, ms-sql, mySql,
postGreSql and oracle.
i think the first iteration of it - i built it in about 2 months of spare
time fiddling.
you may want to take a hard look at making yer own sql pre-processor util.
Regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net
"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.
|
