> because you are to lazy to write proper group by logic. > I am surmising you mean I am "to lazy" (sic) in a good way. Well, perhaps in the estimation of others I am "too" lazy to write "Good SQL" as in VFP9. My VFP7 code runs just fine as it is and there is no need for me to go back and recompile in VFP9, and use "Good SQL" just for the sake of doing it. My time is better spent in ProFox than making needless retro-corrections <g>.
Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Stephen Russell > Sent: Wednesday, June 18, 2008 10:11 AM > To: [EMAIL PROTECTED] > Subject: Re: SQL Select - you think for me, I have a head cold. > > > On Wed, Jun 18, 2008 at 8:06 AM, Gil Hale <[EMAIL PROTECTED]> wrote: > > > > I will respectfully disagree with those who will say use SET > > > ENGINEBEHAVIOR 70. > > > > > > > I use it all the time for my code. There are some pretty cool > things I can > > do Quick, Dirty & Simple using 70 that I find needlessly restrictive or > > tedious in 90. And the way I use 70 I do not seem to run into > any unusual > > results. For some of my apps I am still compiling in VFP7, as I do not > > need > > or want to put my clients through the grief of uninstalling/reinstalling > > just to get the VFP9 runtime and support files registered on their > > machinery. But I do code in VFP9, using care to SET > ENGINEBEHAVIOR 70 and > > to not use any commands or syntax from VFP8/9. All my newer > stuff is VFP9, > > and I often use SET ENGINEBEHAVIOR 70 to get the results I need. Works > > fine, less restrictive, despite not being pure and pristine. > > > > Gil > > > --------------------------------------------------------------------- > > You may find that an audit of your results finds your data inaccurate. If > that were to happen in say a commission report you could find that the > leverage of the salesmanager is stronger then anyone in IT. > > So learn to write compliant SQL instead of a dirty SQL that could > be tainted > because you are to lazy to write proper group by logic. > > I have some case statements that are 10 lines long per statement. > well that > all gets set into the group by as well. > > > > > -- > Stephen Russell > Sr. Production Systems Programmer > Mimeo.com > Memphis TN > > 901.246-0159 > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ 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.
