MB Software Solutions General Account wrote: > Stephen Russell wrote: >> On Thu, Jun 5, 2008 at 11:30 AM, Ricardo Araoz <[EMAIL PROTECTED]> wrote: >> >>> Maybe I'm not getting the point. You are having trouble sending long SQL >>> commands using SQL passthrough? I solve that by having the SQL command >>> in a memo field (in a table or a cursor created to hold the command) and >>> feeding the memo field directly to SQLExec(). I'm currently working with >>> select statements in excess of 5 A4 pages when printed. For comments I >>> use "--" (I send the commands to SQL Server) and don't strip them. >>> -------------------------------------------------------------------- > > > Holy cow.....how can that be good SQL? >
Is there 'bad' SQL? When the specification of your result set is very complicated and requires querying 15 different tables and you tend to properly indent your selects I can guarantee you'll easily get to pass 5 pages. Just today I was reviewing a 17!!!!! (yes, seventeen) page select. It is not the way I'll end up doing it (it has 'evolved') but first I will keep tinkering with it till we get it right and then I'll redesign. Anyway it will certainly end up having more than 12 pages at least. I've had to draw three decision trees in Visio in order to keep track of the bloody thing. _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
