Re: [U2] UniBasic SELECT
Keith: Victory... The F.ICC argument was from an open statement... Open 'INV.CLASS.CODE' to F.ICC else null When the command was changed from SELECT F.ICC... To Execute SELECT INV.CLASS.CODE... The pesky SQL+ prompt went away. Thanks very much indeed for the help. I appreciate it. Regards, --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Keith Johnson [DATACOM] Sent: Sunday, July 31, 2011 5:02 PM To: 'u2-users@listserver.u2ug.org' Subject: Re: [U2] UniBasic SELECT The problem may be in the use of program variables in the executed code. Using Universe, if I have code: VERB = 'SELECT VOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result 237 record(s) selected to SELECT list #0. 237 If I change the filename to something that doesn't exit, like VVOC VERB = 'SELECT vVOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result SQL+ Where I have to press Return to get past this and then get UniVerse/SQL: syntax error. Unexpected verb. Token was SELECT. Scanned command was SELECT -1 Is F.ICC the name of the file in VOC or only internal to the program? Regards, Keith. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
I think that SQL prompt only appears if the filename does not exist, or your VOC pointer is off, etc. In this case, thats what happened, because you were using the file open variable instead of the actual filename perhaps? Sounds like you figured it out :) On Mon, Aug 1, 2011 at 3:06 PM, Bill Brutzman bi...@hkmetalcraft.comwrote: Keith: Victory... The F.ICC argument was from an open statement... Open 'INV.CLASS.CODE' to F.ICC else null When the command was changed from SELECT F.ICC... To Execute SELECT INV.CLASS.CODE... The pesky SQL+ prompt went away. Thanks very much indeed for the help. I appreciate it. Regards, --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto: u2-users-boun...@listserver.u2ug.org] On Behalf Of Keith Johnson [DATACOM] Sent: Sunday, July 31, 2011 5:02 PM To: 'u2-users@listserver.u2ug.org' Subject: Re: [U2] UniBasic SELECT The problem may be in the use of program variables in the executed code. Using Universe, if I have code: VERB = 'SELECT VOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result 237 record(s) selected to SELECT list #0. 237 If I change the filename to something that doesn't exit, like VVOC VERB = 'SELECT vVOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result SQL+ Where I have to press Return to get past this and then get UniVerse/SQL: syntax error. Unexpected verb. Token was SELECT. Scanned command was SELECT -1 Is F.ICC the name of the file in VOC or only internal to the program? Regards, Keith. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- John Thompson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
The problem may be in the use of program variables in the executed code. Using Universe, if I have code: VERB = 'SELECT VOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result 237 record(s) selected to SELECT list #0. 237 If I change the filename to something that doesn't exit, like VVOC VERB = 'SELECT vVOC LIKE A...' EXECUTE VERB CRT @SELECTED CLEARSELECT I get the result SQL+ Where I have to press Return to get past this and then get UniVerse/SQL: syntax error. Unexpected verb. Token was SELECT. Scanned command was SELECT -1 Is F.ICC the name of the file in VOC or only internal to the program? Regards, Keith. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
#1 - Why would you want to change a Basic SELECT to EXECUTE a SELECT? #2 - If you still want to do this, change this: Execute SELECT F.ICC to LIST.2 To this: Execute SELECT F.ICC to :LIST.2 Larry Hiscock Western Computer Services -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman Sent: Friday, July 29, 2011 3:14 PM To: U2 Users List Subject: [U2] UniBasic SELECT In an inherited legacy app, I have a few commands like LIST.1 = 1 LIST.2 = 2 LIST.3 = 3 LIST.4 = 4 SELECT F.ICC to LIST.2 SELECT F.ICC to LIST.3 SELECT F.ICC to LIST.4 And then LIST.2 LIST.3 and LIST.4 show up in loops such as ... loop readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key . . Repeat The red warning marks on the right of the Rocket BDT IDE indicate... expecting INTEGER, found LIST.2 Notwithstanding the red warnings, the program compiles and runs ok. When I try to encapsulate these commands with Execute SELECT F.ICC to LIST.2 The red warnings go away... the program runs ok but, I get a SQL+ prompt after the report prints which can be resolved by just hitting Enter. I do not want my end users to have to deal with (for them) an unusual SQL+ prompt. Suggested work-arounds to make the SQL+ prompt go away would be appreciated. --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
On 29/07/11 23:14, Bill Brutzman wrote: In an inherited legacy app, I have a few commands like LIST.1 = 1 LIST.2 = 2 LIST.3 = 3 LIST.4 = 4 SELECT F.ICC to LIST.2 SELECT F.ICC to LIST.3 SELECT F.ICC to LIST.4 And then LIST.2 LIST.3 and LIST.4 show up in loops such as ... loop readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key . . Repeat The red warning marks on the right of the Rocket BDT IDE indicate... expecting INTEGER, found LIST.2 Notwithstanding the red warnings, the program compiles and runs ok. When I try to encapsulate these commands with Execute SELECT F.ICC to LIST.2 The red warnings go away... the program runs ok but, I get a SQL+ prompt after the report prints which can be resolved by just hitting Enter. I do not want my end users to have to deal with (for them) an unusual SQL+ prompt. Suggested work-arounds to make the SQL+ prompt go away would be appreciated. Because SELECT F.ICC to LIST.2 in basic is COMPLETELY different to SELECT F.ICC to LIST.2 in RETRIEVE. The original expecting integer warning is probably because the compiler is expecting a literal, not a variable. But by enclosing it in quotes and wrapping it in an EXECUTE, you've just converted LIST.2 from being an integer variable to a string literal - a completely different beast. Try instead changing LIST.2 = 2 to EQUATE LIST.2 TO 2 etc, and see if that gets rid of all your warnings. --Bill Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
Thanks to Larry and Wol for writing. Both ways work to get rid of the red warnings but both ways I still get the pesky SQL+ prompt at the end. I only want to change the Basic SELECT to execute SELECT... because this technique makes the Rocket BDT IDE red warning flag go away. When I started migrating programs to BDT, I found that changing CLEARSELECT ALL to execute CLEARSELECT ALL was an easy clean fix to the IDE warnings. --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists Sent: Friday, July 29, 2011 6:37 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UniBasic SELECT On 29/07/11 23:14, Bill Brutzman wrote: In an inherited legacy app, I have a few commands like LIST.1 = 1 LIST.2 = 2 LIST.3 = 3 LIST.4 = 4 SELECT F.ICC to LIST.2 SELECT F.ICC to LIST.3 SELECT F.ICC to LIST.4 And then LIST.2 LIST.3 and LIST.4 show up in loops such as ... loop readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key . . Repeat The red warning marks on the right of the Rocket BDT IDE indicate... expecting INTEGER, found LIST.2 Notwithstanding the red warnings, the program compiles and runs ok. When I try to encapsulate these commands with Execute SELECT F.ICC to LIST.2 The red warnings go away... the program runs ok but, I get a SQL+ prompt after the report prints which can be resolved by just hitting Enter. I do not want my end users to have to deal with (for them) an unusual SQL+ prompt. Suggested work-arounds to make the SQL+ prompt go away would be appreciated. Because SELECT F.ICC to LIST.2 in basic is COMPLETELY different to SELECT F.ICC to LIST.2 in RETRIEVE. The original expecting integer warning is probably because the compiler is expecting a literal, not a variable. But by enclosing it in quotes and wrapping it in an EXECUTE, you've just converted LIST.2 from being an integer variable to a string literal - a completely different beast. Try instead changing LIST.2 = 2 to EQUATE LIST.2 TO 2 etc, and see if that gets rid of all your warnings. --Bill Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
LIST.2 is a variable inside your databasic code. EXECUTE runs some TCL code and is not privy to your databsic variables. I presume you want to concatenate LIST.2 to the end of the execute command and not include it in the string -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman Sent: 29 July 2011 23:14 To: U2 Users List Subject: [U2] UniBasic SELECT In an inherited legacy app, I have a few commands like LIST.1 = 1 LIST.2 = 2 LIST.3 = 3 LIST.4 = 4 SELECT F.ICC to LIST.2 SELECT F.ICC to LIST.3 SELECT F.ICC to LIST.4 And then LIST.2 LIST.3 and LIST.4 show up in loops such as ... loop readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key . . Repeat The red warning marks on the right of the Rocket BDT IDE indicate... expecting INTEGER, found LIST.2 Notwithstanding the red warnings, the program compiles and runs ok. When I try to encapsulate these commands with Execute SELECT F.ICC to LIST.2 The red warnings go away... the program runs ok but, I get a SQL+ prompt after the report prints which can be resolved by just hitting Enter. I do not want my end users to have to deal with (for them) an unusual SQL+ prompt. Suggested work-arounds to make the SQL+ prompt go away would be appreciated. --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users - No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1390 / Virus Database: 1518/3793 - Release Date: 07/28/11 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
On 29/07/11 23:53, Bill Brutzman wrote: Thanks to Larry and Wol for writing. Both ways work to get rid of the red warnings but both ways I still get the pesky SQL+ prompt at the end. That sounds weird. I was wondering why the EXECUTE made the SQL+ prompt appear, but there's no way a BASIC SELECT should do that? I only want to change the Basic SELECT to execute SELECT... because this technique makes the Rocket BDT IDE red warning flag go away. When I started migrating programs to BDT, I found that changing CLEARSELECT ALL to execute CLEARSELECT ALL was an easy clean fix to the IDE warnings. Changing a BASIC statement to a RETRIEVE statement is actually a quite computer-expensive fix ... you want to *get* *rid* of EXECUTEs, not add them! But I can't see how your original code could cause a sql select to occur, nor can I see why my changes would cause it to occur. If your original code doesn't cause the sql+ stuff, then I'd simply get rid of the LIST.2 etc, and change to using a basic select as follows: SELECT F.ICC to 2 That should get rid of the IDE warning, but I'd also raise a ticket with ROCKET about the IDE complaining that it wants an integer, when an integer variable works just as well. And about stuff like your clearselect ... it really should not be encouraging bad practice like that! Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniBasic SELECT
Already mentioned, changing a UniBasic SELECT to an EXECUTE SELECT... is changing the very fundamental definition of what you're doing. The UniBasic SELECT is, for lack of a better way to define it, a delayed select that does not actually go through the file right then and actually select the keys. It pretty much just creates a pointer to the file that is moved with each READNEXT, or whatever command. The EXECUTE SELECT... is a fully finished command that creates the select list in whatever select queue it has been directed to. By default, without a TO clause, it's select list 0. Personally, I like the equate option suggested but myself, I'd just use the actual constant numbers since equates and variables are a lot more typing and don't REALLY add anything to readability or documentation of the code. BobW -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman Sent: Friday, July 29, 2011 3:53 PM To: U2 Users List Subject: Re: [U2] UniBasic SELECT Thanks to Larry and Wol for writing. Both ways work to get rid of the red warnings but both ways I still get the pesky SQL+ prompt at the end. I only want to change the Basic SELECT to execute SELECT... because this technique makes the Rocket BDT IDE red warning flag go away. When I started migrating programs to BDT, I found that changing CLEARSELECT ALL to execute CLEARSELECT ALL was an easy clean fix to the IDE warnings. --Bill -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists Sent: Friday, July 29, 2011 6:37 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UniBasic SELECT On 29/07/11 23:14, Bill Brutzman wrote: In an inherited legacy app, I have a few commands like LIST.1 = 1 LIST.2 = 2 LIST.3 = 3 LIST.4 = 4 SELECT F.ICC to LIST.2 SELECT F.ICC to LIST.3 SELECT F.ICC to LIST.4 And then LIST.2 LIST.3 and LIST.4 show up in loops such as ... loop readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key . . Repeat The red warning marks on the right of the Rocket BDT IDE indicate... expecting INTEGER, found LIST.2 Notwithstanding the red warnings, the program compiles and runs ok. When I try to encapsulate these commands with Execute SELECT F.ICC to LIST.2 The red warnings go away... the program runs ok but, I get a SQL+ prompt after the report prints which can be resolved by just hitting Enter. I do not want my end users to have to deal with (for them) an unusual SQL+ prompt. Suggested work-arounds to make the SQL+ prompt go away would be appreciated. Because SELECT F.ICC to LIST.2 in basic is COMPLETELY different to SELECT F.ICC to LIST.2 in RETRIEVE. The original expecting integer warning is probably because the compiler is expecting a literal, not a variable. But by enclosing it in quotes and wrapping it in an EXECUTE, you've just converted LIST.2 from being an integer variable to a string literal - a completely different beast. Try instead changing LIST.2 = 2 to EQUATE LIST.2 TO 2 etc, and see if that gets rid of all your warnings. --Bill Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users - No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1390 / Virus Database: 1518/3796 - Release Date: 07/29/11 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
RE: [U2] unibasic select woes
Thank you. The 'word'... format is the answer to a question that had me banging my head yesterday. David Morelli, UIS/Datatel Team -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andre Meij Sent: Wednesday, May 30, 2007 5:10 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] unibasic select woes Greg, Actually the following in saver: SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE 'SC'... (note the extra ' around the text) there are a few alphanumeric characters that are interpreted by SELECT and it will show you weird results when you are not expecting that. Regards, Andre -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: maandag 30 april 2007 11:12 To: u2-users@listserver.u2ug.org; u2-users@listserver.u2ug.org Subject: RE: [U2] unibasic select woes Dave, Wyatt Karen, Thank you so much for the tips! Works like a charm! Thanks again, Greg At 12:45 PM 5/30/2007, Dave Davis wrote: In ECLTYPE u SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE SC... If you are currently in ECLTYPE p, you can put the word SELECT in lowercase to evaluate using the u parser. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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/ --- 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] unibasic select woes
In ECLTYPE u SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE SC... If you are currently in ECLTYPE p, you can put the word SELECT in lowercase to evaluate using the u parser. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
Create a new dictionary item with conversion code 'MCU' pointing at the same attribute#. Use that dictionary item in your select. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
Create an I-Type pointing to the text field that converts all the text to upper case and use it in the select I-Type: UP.HRP.LAST.NAME 001: I 002: OCONV(HRP.LAST.NAME,'MCU') 003: 004: LAST NAME 005: 25L 006: S Greg Schraiber wrote: How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- Jeff Schasny - Denver, Co, USA jschasnyATgmailDOTcom --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] unibasic select woes
Try: SELECT HRPER WITH EVAL UPCASE(HRP.LAST.NAME) LIKE 'SC...' -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 12:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
Thanks Karen! Is there really no other way? Seems odd that you can't use functions in the select statement. Greg At 12:42 PM 5/30/2007, Karen Bessel wrote: Create a new dictionary item with conversion code 'MCU' pointing at the same attribute#. Use that dictionary item in your select. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
Hi Greg, Create a dictionary item named, for example, U.HRP.LAST.NAME, and defined as 001: I 002: UPCASE(HRP.LAST.NAME) Fields 3 onwards as for HRP.LAST.NAME Then do SELECT HRPER WITH U.HRP.LAST.NAME LIKE 'SC...' Alternatively, do SELECT HRPER WITH EVAL UPCASE(HRP.LAST.NAME) LIKE 'SC...' Martin Phillips, Ladybridge Systems Ltd --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] unibasic select woes
Greg Schraiber wrote: How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? One solution is to add another dictionary item and uppercase it through the conversion field of the dictionary item. One of the great strengths (and weaknesses) of U2 is that you can have multiple dictionary items defining the same data field. Which sometimes makes it difficult to figure out what the data is supposed to look like, but if organized properly lends itself to selecting and reporting. -- Allen Egerton aegerton at pobox dot com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] unibasic select woes
Dave, Wyatt Karen, Thank you so much for the tips! Works like a charm! Thanks again, Greg At 12:45 PM 5/30/2007, Dave Davis wrote: In ECLTYPE u SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE SC... If you are currently in ECLTYPE p, you can put the word SELECT in lowercase to evaluate using the u parser. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
The EVAL function that someone else mentioned also should work. I've never used it personally so I forgot about that. :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:52 PM To: u2-users@listserver.u2ug.org; u2-users@listserver.u2ug.org Subject: RE: [U2] unibasic select woes Thanks Karen! Is there really no other way? Seems odd that you can't use functions in the select statement. Greg At 12:42 PM 5/30/2007, Karen Bessel wrote: Create a new dictionary item with conversion code 'MCU' pointing at the same attribute#. Use that dictionary item in your select. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] unibasic select woes
Create a new dictionary item like the following: ED DICT HRPER UPC.HRP.LAST.NAME 001: V 002: OCONV(HRP.LAST.NAME, MCU) 003: 004: 005: 10L 006: S SELECT HRPER WITH UPC.HRP.LAST.NAME LIKE 'SC...' Bruce W. McAdoo Wagner Brown, Ltd. [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 12:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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] unibasic select woes
SELECT HRPER WITH HRP.LAST.NAME CONV MCU LIKE 'SC...' Should work. -Original Message- How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] unibasic select woes
Greg, Actually the following in saver: SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE 'SC'... (note the extra ' around the text) there are a few alphanumeric characters that are interpreted by SELECT and it will show you weird results when you are not expecting that. Regards, Andre -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: maandag 30 april 2007 11:12 To: u2-users@listserver.u2ug.org; u2-users@listserver.u2ug.org Subject: RE: [U2] unibasic select woes Dave, Wyatt Karen, Thank you so much for the tips! Works like a charm! Thanks again, Greg At 12:45 PM 5/30/2007, Dave Davis wrote: In ECLTYPE u SELECT HRPER WITH EVAL OCONV(HRP.LAST.NAME,'MCU') LIKE SC... If you are currently in ECLTYPE p, you can put the word SELECT in lowercase to evaluate using the u parser. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Schraiber Sent: Wednesday, May 30, 2007 1:28 PM To: u2-users@listserver.u2ug.org Subject: [U2] unibasic select woes How does one select alpha-numeric data from a unidata datafile using SELECT when the case of the text is not known? I have tried things like: SELECT HRPER WITH UPCASE(HRP.LAST.NAME) LIKE 'SC...' but all I get is a syntax error. Can someone tell me which function(s) can be used to facilitate this type of search? Any help is greatly appreciated! Thank you, Greg --- 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
