This is the notorious matching issue 1A is a valid match string for 1 alphabetic character.
> From: [email protected] > To: [email protected] > Date: Tue, 14 Apr 2009 12:06:30 -0400 > Subject: [U2] Select Problem > > I have just encountered an inconsistency between the native UniData select and the PICK flavored select. > > From a PICK flavored account, it I use the lower case "sselect" to force native UniData syntax, I get: > sselect ITMMST WITH F2 LIKE "...J1A..." (6,213 keys - wrong) > If I immediately follow this with the PICK select: > SELECT ITMMST WITH F2 = "[J1A]" (No keys - correct) > > These two statements SHOULD return the same results. Interestingly, if I use a less restrictive select (search for J1 instead of J1A), I get the following: > sselect ITMMST WITH F2 LIKE "...J1..." (188 keys which is correct) > > I am guessing that the UniData flavor is treating the J1A as something else, but until I can figure out what it is doing, I can not come up with a work-around. > > > > John Israel > Sr. Programmer/Analyst > Dayton Superior Corporation > 721 Richard St. > Dayton, OH 45342 > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ _________________________________________________________________ Rediscover Hotmail.: Now available on your iPhone or BlackBerry http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Mobi le1_042009 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
