Well Gene -
Just remember -
different pieces of a sql statement have some kind of delimitation.
if it's field list, you gots a comma until the last field
if it's line continuances, you gots a semi-colon
for somethings, you might have a + sign, depending on how yer
concactenating
the sql statement
on top of that, I took advantage of the <<text>> <<endtext>> bits inside
of
the utility, at the end part,
and did a bunch of evals inside of it.
I can't say it's a pretty chunk of code , but it does check for proper
punctuation and ORDER of things, then rebuilds it into
whichever sql standard it's about to be processed on (VFP, Oracle, mySql,
ms-sql).
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:iicin31t2aic7isc7q62dsjds5vofa7agl@[EMAIL PROTECTED]
> "swdev2" <wsanders@[EMAIL PROTECTED]
> wrote:
>
> >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.
>
> Details, please?
>
> Sincerely,
>
> Gene Wirchenko
>
> Computerese Irregular Verb Conjugation:
> I have preferences.
> You have biases.
> He/She has prejudices.
|
