On 3/13/2013 12:09 PM, Fred Taylor wrote:
On Wed, Mar 13, 2013 at 8:55 AM, MB Software Solutions, LLC <
[email protected]> wrote:
On 3/13/2013 10:11 AM, Frank Cazabon wrote:
OK, forgive my reformatting of your SQL, I just find using TEXT END and
laying out the SQL this way is much clearer and easier to make changes.
TEXT TO m.lcSql NOSHOW TEXTMERGE
SELECT sitename ;
,siteday;
,progstats.season ;
,COUNT(DATE) AS nights_open ;
,IIF(EMPTY(siteinfo.**deactivated),.T.,.F.) AS ActiveStatus ;
,SUM(fed) AS sum_fed
,SUM(sleep) AS sum_sleep;
,SUM(men) AS sum_men
,SUM(women) AS sum_women;
,SUM(youth) AS sum_youth ;
,siteinfo.siteid
,siteinfo.deactivated ;
FROM progstats ;
<snipped>
I'd offer a quick comment that the semicolons are not necessary if you use
the PRETEXT 15 clause, plus you're that much more ready and not having to
rewrite this code if you send it against a remote RDBMS server.
As long as your final SQL statement is not longer than 255 characters, then
the PRETEXT 15 is OK.
To clarify--I was saying he should use the PRETEXT 15
--
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://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.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.
