Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Pete Sass
  Where is Pete Sass?
 Marathon, Ontario
 Canada
 Pete Sass
 To: Cecil Champenois
  Where is Cecil Champenois?
 Little Elm
 Texas - United States
 Cecil Champenois
 Tags
Subject: RE: Over-Killed Dupes in SQL Statement
Thread ID: 396048 Message ID: 396215 # Views: 35 # Ratings: 0
Version: Visual FoxPro 9 SP2 Category: Databases, Tables and SQL Server
Date: Thursday, January 23, 2014 4:07:46 PM         
   


> >
> >
> > Duplicate post of the above. So might as well use this for Cecil:
> >
> > Personally, I don't see that trying to fit every thing in a single SQL SELECT will be better or worse. It is not about having to look cool anyway with the source codes but to get things done properly. So in some cases, I do like yours, two SQL SELECTs.
> >
> > Anyway, I just wanted to add two not so important things on the above SQL SELECTs:
> >
> > 1. I prefer SQL's BETWEEN clause than BETWEEN() function of VFP (learned that from Anders)
> >
> >
cv.CHG_DATE BETWEEN ldBegin AND ldEnd 
> > 

> >
> > 2. Use mdots on variables to avoid ambiguity:
> >
> >
cv.CHG_DATE BETWEEN m.ldBegin AND m.ldEnd 
> > 

> >
> >
> >
> >
> >
> > https://vfpx.codeplex.com/releases/view/99045
> > http://sandstorm36.blogspot.com
>
> In all of my FoxPro years, I might have used the SQL BETWEEN in a SQL statement maybe once, I have always used the FoxPro function BETWEEN() in FoxPro SQL statements. Time to adjust.
>
> But, I must ask "What difference does it make" to use m.dots or not? (Do I sound like Hillary when she was being interviewed by a congressional panel about Benghazi?
>
> Cecil Champenois, Jr.


Hi Cecil,

If you read past threads "and I do not want to start another m.dots debate", lol
Simply read this Wiki thread for the basic concepts.
http://fox.wikis.com/wc.dll?Wiki~EssentialMDot

Pete "the IceMan", from the Great White North of Canada.
www.marathongriffincomputers.com

ENTIRE THREAD

Over-Killed Dupes in SQL Statement Posted by Cecil Champenois @ 1/22/2014 2:29:01 PM
RE: Over-Killed Dupes in SQL Statement Posted by Tore Bleken @ 1/22/2014 3:04:05 PM
RE: Over-Killed Dupes in SQL Statement Posted by Jun Tangunan @ 1/23/2014 3:18:33 AM
RE: Over-Killed Dupes in SQL Statement Posted by Jun Tangunan @ 1/23/2014 3:18:39 AM
RE: Over-Killed Dupes in SQL Statement Posted by Cecil Champenois @ 1/23/2014 12:59:22 PM
RE: Over-Killed Dupes in SQL Statement Posted by Ali Koumaiha @ 1/23/2014 4:07:24 PM
RE: Over-Killed Dupes in SQL Statement Posted by Pete Sass @ 1/23/2014 4:07:46 PM
RE: Over-Killed Dupes in SQL Statement Posted by Cecil Champenois @ 1/23/2014 5:28:11 PM
RE: Over-Killed Dupes in SQL Statement Posted by Gene Wirchenko @ 1/23/2014 7:58:52 PM
RE: Over-Killed Dupes in SQL Statement Posted by Jun Tangunan @ 1/24/2014 12:05:00 AM
RE: Over-Killed Dupes in SQL Statement Posted by Anders Altberg @ 1/25/2014 1:31:47 AM
RE: Over-Killed Dupes in SQL Statement Posted by Christian Tabligan @ 1/25/2014 2:32:49 PM