Re: SQL Behavior

2009-02-17 Thread Ken Kixmoeller/fh
Hey, Ed - - I re-read your post -- now I understand point you were making. I'm sorry. I hope you can see how using words like "sloppy" could put one on the defensive. Ken On Feb 16, 2009, at 10:39 PM, Ed Leafe wrote: > On Feb 16, 2009, at 8:21 PM, Ken Kixmoeller/fh wrote: > >> Holy Smoke!

Re: SQL Behavior

2009-02-16 Thread Ed Leafe
On Feb 16, 2009, at 8:21 PM, Ken Kixmoeller/fh wrote: > Holy Smoke! Such pedantry over one innocent question. It's not pedantry; it's simply the difference between correct programming and good enough programming. That was my point: while asking for data that is not needed is not corr

Re: SQL Behavior

2009-02-16 Thread Ken Kixmoeller/fh
Holy Smoke! Such pedantry over one innocent question. If you can step down off the pedestal for a moment, for some perspective: This is one SQL statement in a nearly 8,000-line conversion program. It is a quick cross-check of information derived by other means. Enginebehavior pops to 70 for

Re: SQL Behavior

2009-02-16 Thread Ed Leafe
On Feb 16, 2009, at 1:10 PM, Stephen Russell wrote: > You can get the wrong data when you don't lay out your group bys > properly. The point is that the wrong data isn't needed. Only a few fields are used; they just want to be able to type 'select *' instead of having to specify th

Re: SQL Behavior

2009-02-16 Thread Ricardo Aráoz
Stephen Russell wrote: > On Mon, Feb 16, 2009 at 9:21 AM, Ken Kixmoeller/fh > wrote: > >> On Feb 16, 2009, at 9:11 AM, Stephen Russell wrote: >> >> >>> or you could crate the correct syntax that groups properly, instead of >>> hoping that it will guess properly. >>> >> This is the s

RE: SQL Behavior

2009-02-16 Thread Matt Jarvis
> -Original Message- > From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] > On Behalf Of Stephen Russell > Sent: Monday, February 16, 2009 11:10 AM > To: profoxt...@leafe.com > Subject: Re: SQL Behavior > > > You can get the wrong data

Re: SQL Behavior

2009-02-16 Thread Stephen Russell
On Mon, Feb 16, 2009 at 9:21 AM, Ken Kixmoeller/fh wrote: > > On Feb 16, 2009, at 9:11 AM, Stephen Russell wrote: > >> or you could crate the correct syntax that groups properly, instead of >> hoping that it will guess properly. > > This is the same conversion program we talked about it earlier. T

Re: SQL Behavior

2009-02-16 Thread Ken Kixmoeller/fh
On Feb 16, 2009, at 9:11 AM, Stephen Russell wrote: > or you could crate the correct syntax that groups properly, instead of > hoping that it will guess properly. This is the same conversion program we talked about it earlier. This is a one-off SQL statement that I will use for the next 3 week

Re: SQL Behavior

2009-02-16 Thread Stephen Russell
On Sat, Feb 14, 2009 at 3:00 PM, Gerald Foote wrote: > Try set enginebehavior 70 > Jerry - or you could crate the correct syntax that groups properly, instead of hoping that it will guess properly. -- Stephen Russell Sr. Production Systems Programmer First Horizon Bank M

RE: SQL Behavior

2009-02-16 Thread Gerald Foote
Try set enginebehavior 70 Jerry -Original Message- From: Kenneth Kixmoeller [mailto:ken.kixmoel...@information-architecture.com] Sent: Saturday, February 14, 2009 9:32 AM To: Profox Subject: SQL Behavior Please, someone, give me a swift kick to the brain: What is the SET command to make

re: SQL Behavior

2009-02-14 Thread Ken Kixmoeller/fh
The magic "Send" button strikes again -- I found it. "Latilla" Ken Begin forwarded message: > Subject: SQL Behavior > > Please, someone, give me a swift kick to the brain: > > What is the SET command to make a SQL statement in VFP9 so you > don't have to GROUP BY every frickin' field in the ta