> > > > the engine doesn't necessarily insist on a specified location > > for other clauses, such as INTO CURSOR. The engine is clearly smart enough > > to parse SQL keywords in more than one location.
Be that as it may, VFP is a lot more forgiving in it's SQL syntax about lots of things like order of clauses than say, T-SQL is. Understood, and not disputed here (though it seems to me that the value of brain-dead parsers vs intelligent parsers would be worth disputing in some forum). I have the ability to grasp that there are multiple implementations of ANSI SQL standards. Really and truly, despite my preference to focus on Foxpro, I am aware of the rest of the computer language universe. However, right now I'm not using T-SQL (and may never; when I go to a separate SQL back end it's not likely to be M$ SQL Server). Right now I'm using Foxpro. I'm interested in whether there is an ANSI SQL standard that says you're not supposed to be able to have "DISTINCT" after the field list. Is there? If not, then there's no bug in allowing such usage, in my opinion. Ken Dibble www.stic-cil.org _______________________________________________ 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.
