> From: Paul Newton <[EMAIL PROTECTED]> > And Stephen and Mike appear to be wrong in their suggestions - see > > http://code-magazine.com/article.aspx?quickid=0404022&page=3 > > If you are not bound by a low memory environment, consider using > SYS(3055) to set the complexity level of the FOR and WHERE clauses to > its maximum value of 2040 when you set up the environment for your > applications. This allows more complex SQL statements and more values > with IN. See the Help files for a list of other commands and functions > that are affected by this setting.
I have taken union segments that set a mighty long select statement together and combined them in end to be around 700+ lines long. This was FPD and not VFP but it still worked. It was normalization of samples from one table of 16 columns SQL='bla bla' Union1='Union all bla bla' Union2='Union all bla bla' Union3='Union all bla bla' Union4='Union all bla bla' Union5='Union all bla bla' Union6='Union all bla bla' Union7='Union all bla bla' Union8='Union all bla bla' Union9='Union all bla bla' Union10='Union all bla bla' Union11='Union all bla bla' Union12='Union all bla bla' Union13='Union all bla bla' Union14='Union all bla bla' Union15='Union all bla bla' lcSQL = SQL + Union1+ Union2+ Union3+ Union4+ Union5+ Union6+ Union7+ Union8+ Union9+ Union10+ Union11+ Union12+ Union13+ Union14+ Union15 I then passed that that string back against a SQL table that was old VAX data in our data warehouse. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
