Have I said lately how much I hate SET RELATION code for report cursors? We've got a report output that is also desired to be an Excel output. Simple if you're using a single cursor...just select the cursor and COPY TO Crap TYPE XL5. But this legacy code uses a bunch of SET RELATIONs and so to export this to Excel requires me to write the code to create that single cursor first. F*ck!!!
Another reason I like single cursors for reporting purposes. -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ 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.
