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. >> -------------------------------------------------------------------- > > > You need to make a view for your huge query and then you can add a where > clause for limiting it's output. >
Mine is an in-house application, a report menu generator where you define your queries in multiple engines and combine them with a fox query, you can define variables (some of which may come from a multi selection list filled with yet another query) and servers from where to get your data, you can get multiple result sets from a menu option and they will be combined into an excel worksheet with multiple pages (you get to define the pages names). The idea is to be able to define a report in a few minutes after you have your select statement ready.So a view would not fill the ticket. _______________________________________________ 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.
