RE: [U2] Select Problem
It's because 1A means one numeric character. If you surround the literal in single quotes it'll work fine: sselect ITMMST WITH F2 LIKE ...'J1A'... (6,213 keys - wrong) Ed -Original Message- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: 14 April 2009 17:07 To: 'u2-users@listserver.u2ug.org' 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- Please remember to recycle wherever possible. Reduce, reuse, recycle, think do you need to print this e-mail? --- This e-mail and any attachment(s), is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the addressee, dissemination, copying or use of this e-mail or any of its content is prohibited and may be unlawful. If you are not the intended recipient please inform the sender immediately and destroy the e-mail, any attachment(s) and any copies. All liability for viruses is excluded to the fullest extent permitted by law. It is your responsibility to scan or otherwise check this email and any attachment(s). Unless otherwise stated (i) views expressed in this message are those of the individual sender (ii) no contract may be construed by this e-mail. Emails may be monitored and you are taken to consent to this monitoring. Civica Services Limited, Company No. 02374268; Civica UK Limited, Company No. 01628868 Both companies are registered in England and Wales and each has its registered office at 2 Burston Road, Putney, London, SW15 6AR. --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Select Problem
It's using it like matching. Jerry Banker -Original Message- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Tuesday, April 14, 2009 11:07 AM To: 'u2-users@listserver.u2ug.org' 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Select Problem
Is it taking 1A as a mask? One Alphanumeric character? How many do you get with ...J...? Charles Shaffer Senior Analyst NTN-Bower Corporation Israel, John R. johnisr...@daytonsuperior.com Sent by: owner-u2-us...@listserver.u2ug.org 04/14/2009 11:06 AM Please respond to u2-users To: 'u2-users@listserver.u2ug.org' u2-users@listserver.u2ug.org cc: 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Select Problem
Thanks for all the replies. Yeah, it was doing a pattern match, but not one that I would have expected. The ...J1A... was returning anything with a J in F2. I am guessing the 1A was causing it to think I wanted anything with alpha in it, though I would have thought the 1A would have returned just a single character match, not any length, and how the J played into this in conjunction with the pattern match is something I have never seen. However, the syntax I ultimately needed was provided by Ed: ...'J1A' Thanks again to all. John Israel Sr. Programmer/Analyst Dayton Superior Corporation 721 Richard St. Dayton, OH 45342 937-866-0711 x44380 -Original Message- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of charles_shaf...@ntn-bower.com Sent: Tuesday, April 14, 2009 2:02 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Select Problem Is it taking 1A as a mask? One Alphanumeric character? How many do you get with ...J...? Charles Shaffer Senior Analyst NTN-Bower Corporation Israel, John R. johnisr...@daytonsuperior.com Sent by: owner-u2-us...@listserver.u2ug.org 04/14/2009 11:06 AM Please respond to u2-users To: 'u2-users@listserver.u2ug.org' u2-users@listserver.u2ug.org cc: 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Select Problem
The 1A in ...J1A... is a valid pattern. So this string will match anything that contains a J followed by an alpha character. If you want to match J1A literally, you need to quote it, i.e. ...J'1A'... or 0X'J1A'0X On Apr 14, 2009, at 12:06 PM, Israel, John R. wrote: 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Select Problem
This is the notorious matching issue 1A is a valid match string for 1 alphabetic character. From: johnisr...@daytonsuperior.com To: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SELECT problem with quote characters
Consider trying... SELECT FILE WITH FIELD LIKE LLOYD'S... --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anthony Youngman Sent: Wednesday, August 06, 2008 11:18 AM To: u2-users@listserver.u2ug.org Subject: [U2] SELECT problem with quote characters I'm trying to select a string that contains a single-quote, using the LIKE operator. It works fine with EQ. So if I do a SELECT FILE WITH FIELD EQ LLOYD'S , the select returns exactly what I expect. But if I do a SELECT FILE WITH FIELD LIKE ...LLOYD'S... it returns pretty much the entire file And if I do a SELECT FILE WITH FIELD LIKE \...LLOYD'S...\ it returns nothing. What on earth is the syntax for picking up an embedded quote in data in a LIKE comparison? PIOPEN flavour, by the way. Cheers, Wol --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SELECT problem with quote characters
LIKE ...LLOYD'S... Nancy Fisher Peninsula Truck Lines, Inc Auburn, Washington Visit our Website www.peninsulatruck.com [EMAIL PROTECTED] - Original Message - From: Anthony Youngman [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, August 06, 2008 8:18 AM Subject: [U2] SELECT problem with quote characters I'm trying to select a string that contains a single-quote, using the LIKE operator. It works fine with EQ. So if I do a SELECT FILE WITH FIELD EQ LLOYD'S , the select returns exactly what I expect. But if I do a SELECT FILE WITH FIELD LIKE ...LLOYD'S... it returns pretty much the entire file And if I do a SELECT FILE WITH FIELD LIKE \...LLOYD'S...\ it returns nothing. What on earth is the syntax for picking up an embedded quote in data in a LIKE comparison? PIOPEN flavour, by the way. Cheers, Wol --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SELECT problem with quote characters
Try the select like this SELECT FILE WITH FIELD LIKE ...LLOYD'S... Dan Goble Systems Administrator RATEX Business Solutions, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Youngman Sent: Wednesday, August 06, 2008 11:18 AM To: u2-users@listserver.u2ug.org Subject: [U2] SELECT problem with quote characters I'm trying to select a string that contains a single-quote, using the LIKE operator. It works fine with EQ. So if I do a SELECT FILE WITH FIELD EQ LLOYD'S , the select returns exactly what I expect. But if I do a SELECT FILE WITH FIELD LIKE ...LLOYD'S... it returns pretty much the entire file And if I do a SELECT FILE WITH FIELD LIKE \...LLOYD'S...\ it returns nothing. What on earth is the syntax for picking up an embedded quote in data in a LIKE comparison? PIOPEN flavour, by the way. Cheers, Wol --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SELECT problem with quote characters
Hi, This is why there are three types of string quote. You need SELECT FILE WITH FIELD LIKE \...LLOYD'S...\ Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
